You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/application-gateway/using-sse.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,12 +25,12 @@ The [Response Buffers on Application Gateway resource](proxy-buffers.md) should
25
25
26
26
### Backend Setting - Request timeout
27
27
28
-
Ensure that the [Request time-out (seconds) in Backend Settings](configuration-http-settings.md?tabs=backendhttpsettings#request-timeout) is configured to exceed the idle time between events. Otherwise, your application gateway resource will terminate the connection prematurely.
28
+
Ensure that the [Request time-out (seconds) in Backend Settings](configuration-http-settings.md?tabs=backendhttpsettings#request-timeout) is configured to exceed the idle time between events. Otherwise, your application gateway resource terminates the connection prematurely.
29
29
30
30
31
31
## Configuring backend server
32
32
33
-
The backend server should send the following Response headers to ensure proper stream handling by the clients and any intermediaries. Note, these headers are not a requirement for Application Gateway as a proxy.
33
+
The backend server should send the following Response headers to ensure proper stream handling by the clients and any intermediaries. Note, these headers aren't a requirement for Application Gateway as a proxy.
34
34
35
35
### Content-Type: text/event-stream
36
36
This header notifies the client that the response will be a stream of events, enabling them to correctly handle the Server-Sent Events (SSE) protocol.
@@ -39,10 +39,10 @@ This header notifies the client that the response will be a stream of events, en
39
39
This header maintains the TCP connection, allowing the backend server to send events to the client continuously.
40
40
41
41
### Transfer-Encoding: chunked
42
-
This header allows the server to send responses in chunks without requiring a Content-Length header. It is necessary for streaming responses through SSE when the total size cannot be determined in advance.
42
+
This header allows the server to send responses in chunks without requiring a Content-Length header. It's necessary for streaming responses through SSE when the total size can't be determined in advance.
43
43
44
44
### Cache-Control: no-cache
45
-
It is generally advisable to use this header to prevent intermediaries like CDNs from caching the SSE response.
45
+
It's advisable to use this header to prevent intermediaries like CDNs from caching the SSE response.
46
46
47
47
## Next steps
48
48
Learn about [Request and Response Proxy Buffers](proxy-buffers.md) in Application Gateway.
0 commit comments