deploy: 8d20b1ba1e
				
					
				
			
							parent
							
								
									7d09b30561
								
							
						
					
					
						commit
						539b491e69
					
				| 
						 | 
				
			
			@ -901,7 +901,7 @@ listens to traffic on localhost. (Do not change <code>bind_addresses</code> to <
 | 
			
		|||
when using a containerized Synapse, as that will prevent it from responding
 | 
			
		||||
to proxied traffic.)</p>
 | 
			
		||||
<p>Optionally, you can also set
 | 
			
		||||
<a href="../usage/configuration/config_documentation.html#listeners"><code>request_id_header</code></a>
 | 
			
		||||
<a href="./usage/configuration/config_documentation.html#listeners"><code>request_id_header</code></a>
 | 
			
		||||
so that the server extracts and re-uses the same request ID format that the
 | 
			
		||||
reverse proxy is using.</p>
 | 
			
		||||
<h2 id="reverse-proxy-configuration-examples"><a class="header" href="#reverse-proxy-configuration-examples">Reverse-proxy configuration examples</a></h2>
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
| 
						 | 
				
			
			@ -184,7 +184,7 @@ listens to traffic on localhost. (Do not change <code>bind_addresses</code> to <
 | 
			
		|||
when using a containerized Synapse, as that will prevent it from responding
 | 
			
		||||
to proxied traffic.)</p>
 | 
			
		||||
<p>Optionally, you can also set
 | 
			
		||||
<a href="../usage/configuration/config_documentation.html#listeners"><code>request_id_header</code></a>
 | 
			
		||||
<a href="./usage/configuration/config_documentation.html#listeners"><code>request_id_header</code></a>
 | 
			
		||||
so that the server extracts and re-uses the same request ID format that the
 | 
			
		||||
reverse proxy is using.</p>
 | 
			
		||||
<h2 id="reverse-proxy-configuration-examples"><a class="header" href="#reverse-proxy-configuration-examples">Reverse-proxy configuration examples</a></h2>
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
		Reference in New Issue