You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2017/02/28 12:04:54 UTC
[Bug 60783] New: HttpProtocolOptions Directive' option Unsafe does
not allow legacy request formats
https://bz.apache.org/bugzilla/show_bug.cgi?id=60783
Bug ID: 60783
Summary: HttpProtocolOptions Directive' option Unsafe does not
allow legacy request formats
Product: Apache httpd-2
Version: 2.4.25
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Core
Assignee: bugs@httpd.apache.org
Reporter: reichl.pavel@gmail.com
Target Milestone: ---
Hello,
In 2.4.23 among others it was legal to use tabs as separator in request line,
or to have SP or TAB between header name and colon. Neither of these works in
2.4.25 even with HttpProtocolOptions set to Unsafe.
Docs say:
...
Due to legacy modules, applications or custom user-agents which must be
deprecated the Unsafe option has been added to revert to the legacy behaviors.
So it would seem that we should get fully legacy behavior with this directive,
or should not we?
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
[Bug 60783] HttpProtocolOptions Directive' option Unsafe does not
allow legacy request formats
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60783
--- Comment #1 from Eric Covener <co...@gmail.com> ---
(In reply to reichl.pavel from comment #0)
> Hello,
>
> In 2.4.23 among others it was legal to use tabs as separator in request
> line, or to have SP or TAB between header name and colon. Neither of these
> works in 2.4.25 even with HttpProtocolOptions set to Unsafe.
>
> Docs say:
> ...
> Due to legacy modules, applications or custom user-agents which must be
> deprecated the Unsafe option has been added to revert to the legacy
> behaviors.
>
> So it would seem that we should get fully legacy behavior with this
> directive, or should not we?
>
No. It looks like the docs may have been reworded, but the design is not to
preserve all of the legacy parsing even under unsafe.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
[Bug 60783] HttpProtocolOptions Directive' option Unsafe does not
allow legacy request formats
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60783
William A. Rowe Jr. <wr...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from William A. Rowe Jr. <wr...@apache.org> ---
See 3.2.4 paragraph 2 of http://www.rfc-base.org/txt/rfc-7230.txt - we have no
choice but to reject whitespace in the header prior to the ':' delimiter,
irrespective of configuration.
W.R.T. tabs in the request line, I proposed such a tweak and was overruled by
the development team; the spec has always called for SP and only single SP
characters since day one of HTTP, so there's no particular reason for an HTTP
server to recognize anything else.
The reason for strictly returning 400 responses, is to ensure we do not
propagate a bad request to an unsuspecting back-end origin server, or fulfill
the request of a too-trusting-but-faulty proxy client.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
[Bug 60783] HttpProtocolOptions Directive' option Unsafe does not
allow legacy request formats
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60783
Michal Karm Babacek <ka...@email.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |karm@email.cz
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org