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
The response messages do not have the Content-Location header. There is no FHIR-style location for an XDS object. The solution is to:
add one that points at the proxy
add a second header x-proxy-no-logging (new) that prevents logging of the transaction even though it travels through the proxy.
The MHD channel would set the Content-Location header on the response message pointing to the proxy (on the client side the content is FHIR so a Content-Location exists). Second, when server content is gathered supporting the Inspect Server function, the x-proxy-no-logging header would be added to all requests. These requests go to the proxy and this header keeps these requests from clogging the proxy event logs.
The text was updated successfully, but these errors were encountered:
The response messages do not have the Content-Location header. There is no FHIR-style location for an XDS object. The solution is to:
The MHD channel would set the Content-Location header on the response message pointing to the proxy (on the client side the content is FHIR so a Content-Location exists). Second, when server content is gathered supporting the Inspect Server function, the x-proxy-no-logging header would be added to all requests. These requests go to the proxy and this header keeps these requests from clogging the proxy event logs.
The text was updated successfully, but these errors were encountered: