Closed GoogleCodeExporter closed 9 years ago
The problem is that the server returned an unsupported HTTP version number.
Which server was used? Is it using a custom HTTP version? Could you provide the
response?
Original comment by THC...@gmail.com
on 25 May 2015 at 9:16
This is a custom server and indeed returns somthing uncommon HTTP/1.4.2015
The "HTTP"- version in response is unimportant, somehow, just to be mentioned.
The same applies to "HTTP" itself in the version field.
That ZAP crashes at this point is a bit strange, as such things (response line)
may be the result of parameter manipulation, i.e. \r\n or a like.
I'd be happy if ZAP handles this properly (I know it's the fault of the used
java library;-)
It'sa warning, error, or detected attack.
My subject line for this defect is wrong then, should be: "uncommon response
line not handled".
Does this all sound reasonable?
Original comment by ac...@owasp.org
on 25 May 2015 at 9:42
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
Original issue reported on code.google.com by
ac...@owasp.org
on 25 May 2015 at 7:55