You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Lueders, Paul T CIV USARMY NGIC (US)" <pa...@mail.mil> on 2017/12/11 14:34:01 UTC
Apache tomcat 7.0.82 RFC issue (UNCLASSIFIED)
CLASSIFICATION: UNCLASSIFIED
I am running Apache tomcat 7.0.82. It is not running behind any other web server. I am getting:
Java.lang.IllegalArgumentException: Invalid Character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986
How can I correct this in the tomcat configuration files?
Thanks a lot,
Paul Lueders
CLASSIFICATION: UNCLASSIFIED
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Apache tomcat 7.0.82 RFC issue (UNCLASSIFIED)
Posted by Mark Thomas <ma...@apache.org>.
On 11 December 2017 14:34:01 GMT+00:00, "Lueders, Paul T CIV USARMY NGIC (US)" <pa...@mail.mil> wrote:
>CLASSIFICATION: UNCLASSIFIED
>
>I am running Apache tomcat 7.0.82. It is not running behind any other
>web server. I am getting:
>Java.lang.IllegalArgumentException: Invalid Character found in the
>request target. The valid characters are defined in RFC 7230 and RFC
>3986
>
>How can I correct this in the tomcat configuration files?
That might not be possible.
Which illegal character (s) are the broken clients sending?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Apache tomcat 7.0.82 RFC issue (UNCLASSIFIED)
Posted by Coty Sutherland <cs...@apache.org>.
On Mon, Dec 11, 2017 at 9:34 AM, Lueders, Paul T CIV USARMY NGIC (US)
<pa...@mail.mil> wrote:
> CLASSIFICATION: UNCLASSIFIED
>
> I am running Apache tomcat 7.0.82. It is not running behind any other web server. I am getting:
> Java.lang.IllegalArgumentException: Invalid Character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986
The problem is that your clients are sending unencoded characters
which are not allowed by the spec. See
https://bz.apache.org/bugzilla/show_bug.cgi?id=60594 or search the
users list archives for 'RFC 7230' or 'RFC 3986' for more information.
> How can I correct this in the tomcat configuration files?
Search for 'tomcat.util.http.parser.HttpParser.requestTargetAllow' in
http://tomcat.apache.org/tomcat-7.0-doc/config/systemprops.html to see
what options are available. Presently you can allow {, }, and | but
other characters will still yield a 400 response.
> Thanks a lot,
>
> Paul Lueders
> CLASSIFICATION: UNCLASSIFIED
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org