Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Record and replay request headers #14

Closed
st3fan opened this issue May 2, 2013 · 1 comment
Closed

Record and replay request headers #14

st3fan opened this issue May 2, 2013 · 1 comment

Comments

@st3fan
Copy link

st3fan commented May 2, 2013

I had a Zest script failing on me because it did not include the Accept: header. As a response the server returned a text/plain response instead of the original HTML document that I saw in ZAP.

Maybe there should be a default set of headers that Zest should always take and replay to make the request look as much as possible as one coming from a browser? How about at least User-Agent:, Accept:, Accept-Language:, Accept-Encoding: ?

@psiinon
Copy link
Member

psiinon commented May 3, 2013

Agreed, but I think this should be a feature of the tool that uses Zest.
Raised as http://code.google.com/p/zaproxy/issues/detail?id=658

@psiinon psiinon closed this as completed May 3, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants