--- Comment #8 from Mark Thomas <> ---
>From memory, the previous parser was lenient to the extent that it only checked
for characters that were not permitted anywhere in the request target rather
than checking each part individually.

My initial thoughts were something pluggable on the connector that delegated
most of the work to the HttpParser which would almost certainly need some new
methods. My thinking hasn't got much beyond that though.

I'm planning on putting together something to map request target part,
characters allowed and specification as I want to get a clearer understanding
of what is and isn't allowed where.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to