search

ashenchowthee / zaproxy

Automatically exported from code.google.com/p/zaproxy
0 stars 0 forks source link

GZip de-compression causes loss of newlines #1584

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Find a URL where the response body contains newlines, and where the server 
supports gzip compression.
2. Send a request for the URL *with* the request header "Accept-Encoding: gzip" 
3. Send a request for the URL *without* the request header "Accept-Encoding: 
gzip" 
4. View both requests by clicking on them in the history tab

What is the expected output? 
The two outputs should match, when ZAP is de-compressing the response for 
display.

What do you see instead?
Currently, the two outputs do not visually match.  The request that was 
specified *with* "Accept-Encoding: gzip" is missing newlines that appear in the 
other request.

Background: 
refer to https://code.google.com/p/zaproxy/issues/detail?id=1346&q=gzip

Please use labels and text to provide additional information.

Original issue reported on code.google.com by colm.p.o...@gmail.com on 30 Mar 2015 at 11:49

GoogleCodeExporter commented 9 years ago 
ZAP has been migrated to github

This issue will be on github issues with the same ID: 
https://github.com/zaproxy/zaproxy/issues

Original comment by psii...@gmail.com on 5 Jun 2015 at 9:18