New
Last Updated: 13 Feb 2019 23:29 by Fergal
Fergal
Created on: 12 Feb 2019 16:16
Type: Bug Report
0
Response headers added on from Fiddler-script (in reverse-proxy setup) are not sent to client. Even though the session shows them as sent? However, if I set a bpafter for that particular url it works!
Response headers added from Fiddler-script (in reverse-proxy setup) are not sent to client. Even though the session shows them as sent. However, if I set a bpafter for that particular url it works! I Don't need to do anything else, just set the bpafter ang type 'g' to let it go. The client then see the response header.
(Total attached files size should be smaller than 20mb. Allowed extensions: .zip, .rar, .jpg, .png, .gif)
2 comments
Fergal
Posted on: 13 Feb 2019 23:29

It works!

using the OnPeekAtResponseHeaders event solves my issue.

Thanks for your quick response and thanks for your great work!

Fergal.

Eric
Posted on: 13 Feb 2019 21:13

The common source of the problem here is that the response was configured to stream, which means that the OnBeforeResponse handler doesn't run until after the response was already streamed to the client.

Add your new header inside the OnPeekAtResponseHeaders handler, or set oSession.bBufferResponse to true in either the OnBeforeRequest handler, or the OnPeekAtResponseHeaders handler.