


How to implement http.Hijacker using Gorilla Websockets and alexedwards/scs/v2
php Editor Apple today introduces a method to implement http.Hijacker using Gorilla Websockets and the alexedwards/scs/v2 library. This method can help developers implement real-time communication functions in their own applications, whether it is a chat room or real-time updates, etc., can be implemented in this way. Next, we will explain in detail how to use these two libraries to implement http.Hijacker to make your application more powerful and flexible.
Question content
The excellent alexedwards/scs/v2 in Go web applications was recently upgraded from 2.5.0 to 2.7.0 to allow Go 1.20 to support http.NewResponseController(). Subsequently allow extension handler specific server write timeout for large file uploads. This is good. An unfortunate consequence of this necessary upgrade is the loss of websocket functionality, currently using Gorilla websockets v1.5.1 (latest). I'm getting a common error when trying to connect to upgrade... websocket: response not implemented http.Hijacker I've looked into a few threads for this, some of them on SO, but I haven't been able to resolve anything specific to this case. I've tried a few things to try and implement http.Hijacker in my websocket endpoint handler along with my other middleware code (commented out, attached "misleading" example for illustration)... I just think I understand this Not good enough. ..
type WebsocketConnection struct { *websocket.Conn } type WebsocketPayload struct { Action string `json:"action"` Message string `json:"message"` AdminName string `json:"admin_name"` MessageType string `json:"message_type"` AdminID int `json:"admin_id"` Connection WebsocketConnection `json:"-"` } type WebsocketJSONResponse struct { Action string `json:"action"` Message string `json:"message"` AdminName string `json:"admin_name"` AdminID int `json:"admin_id"` CurrentLogins []string `json:"current_logins"` } var upgradeConnection = websocket.Upgrader{ ReadBufferSize: 1024, WriteBufferSize: 1024, CheckOrigin: func(r *http.Request) bool { return true }, } var webClients = make(map[WebsocketConnection]string) var websocketChannel = make(chan WebsocketPayload) func (app *application) WebsocketEndPoint(w http.ResponseWriter, r *http.Request) { // rc := http.NewResponseController(w) // netConn, _, err := rc.Hijack() // if err != nil { // app.errorLog.Println(err) // return // } // defer netConn.Close() app.debugLog.Printf("w's type is %T\n", w) ws, err := upgradeConnection.Upgrade(w, r, nil) if err != nil { app.errorLog.Println(err) <= ERROR HERE return } app.infoLog.Printf("Web client connected from %s", r.RemoteAddr) var response WebsocketJSONResponse response.Message = "Connected to server..." err = ws.WriteJSON(response) if err != nil { app.errorLog.Println(err) return } conn := WebsocketConnection{Conn: ws} webClients[conn] = "" go app.ListenForWebsocket(&conn) }
The "w" in this example is *scs.sessionResponseWriter. How can I implement http.Hijacker in the response without breaking the connection and upgrading? What is the correct approach?
Workaround
alexedwards/scs/v2 package version 2.5.0 Supports hijacker interface. Version 2.7.0 does not support Hijacker interface, but supports Support response controller. The gorilla websocket package does not use response controllers.
Option 1
2.5.0 using alexedwards/scs/v2 package.
Option 2
Work around the gorilla package flaw by unpacking the response writer in the application code:
func (app *application) WebsocketEndPoint(w http.ResponseWriter, r *http.Request) { wupgrade := w if u, ok := w.(interface{ Unwrap() http.ResponseWriter }); ok { wupgrade = u.Unwrap() } app.debugLog.Printf("w's type is %T\n", w) ws, err := upgradeConnection.Upgrade(wupgrade, r, nil) if err != nil { app.errorLog.Println(err) return } app.infoLog.Printf("Web client connected from %s", r.RemoteAddr) var response WebsocketJSONResponse response.Message = "Connected to server..." err = ws.WriteJSON(response) if err != nil { app.errorLog.Println(err) return } conn := WebsocketConnection{Conn: ws} webClients[conn] = "" go app.ListenForWebsocket(&conn) }
The above is the detailed content of How to implement http.Hijacker using Gorilla Websockets and alexedwards/scs/v2. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

The article explains how to use the pprof tool for analyzing Go performance, including enabling profiling, collecting data, and identifying common bottlenecks like CPU and memory issues.Character count: 159

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...
