Me ya sa haɗuwar WebSocket take gaza ta Nginx?

Question

IT Interview Practice · Accepted Answer

Da farko bambanta handshake da ya gaza daga haɗuwar da ta buɗe sannan ta rufe daga baya. Alamomin biyu suna kaiwa ga bincike daban.

## Bari manhajar ta karɓi buƙatar upgrade

Ga route ta WebSocket ta musamman, sanya wannan cikin `server`:

```nginx
location /socket/ {
    proxy_pass http://127.0.0.1:3000;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
}
```

`proxy_http_version` yana amfani da HTTP/1.1 kai tsaye zuwa backend. `Upgrade` yana tura canjin protocol da client ya nema. `Connection` yana gaya wa backend cewa wannan haɗuwar tana neman canjin. Dole a tura waɗannan headers a fili domin proxies ba sa tura kowane header na musamman ga haɗuwa kawai.

## Karanta sakamakon

Handshake mai nasara yana mayar da `101 Switching Protocols`. Idan ka samu 404, duba hanyar backend; idan authentication ya gaza, binciki policy na manhajar. Proxy configuration ba ya maye gurbin authentication ko gwajin origins da aka yarda.

Idan haɗuwar ta buɗe amma ta rufe bayan rashin aiki, duba idle timeouts na Nginx da sauran proxies. Yi amfani da WebSocket ping frames daga server da `proxy_read_timeout` da ya dace tare da halayyar client ta sake haɗuwa. Ƙara timeout kaɗai zai iya riƙe matattun haɗe-haɗe na dogon lokaci.

[Takardun hukuma](https://nginx.org/en/docs/http/websocket.html).

Bari manhajar ta karɓi buƙatar upgrade

Karanta sakamakon

Tambayoyi masu alaƙa