Java error since upgrade to 5.2 and to Tomcat 7.0.70

Post any questions regarding Installing or Upgrading Ebase, including problems starting up the Ebase Xi Server or Designer

Moderators: Ian, Dave, jcoulson, Jon, Wai

neilnewman
Ebase User
Posts: 162
Joined: Fri Dec 20, 2013 1:29 pm
Location: Dartford Borough Council
Contact:

Java error since upgrade to 5.2 and to Tomcat 7.0.70

#1

Postby neilnewman » Fri Feb 24, 2017 11:55 am

We have a few forms that make a call thus from a jsp script prior to displaying the form:
form.callUrl ("http://<SERVERNAME>/GetUserNameRedirectUrl.aspx", parms,form.HTTP_PROTOCOL_GET);

This aspx file returns the users AD user name thus: DBC\nnewman

It appears that since the upgrade it does not like the "\" in the returned URL:
http://dbc-daap-18:3040/ufs/ufsreturn?e ... BC\nnewman

The error log shows:
Feb 24, 2017 11:15:10 AM org.apache.coyote.http11.AbstractHttp11Processor process
INFO: Error parsing HTTP request header
Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986
at org.apache.coyote.http11.InternalAprInputBuffer.parseRequestLine(InternalAprInputBuffer.java:235)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1000)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2536)
at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2525)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source)

Anyone come across this problem and found a work around PLEASE.
0 x

Jon
Moderator
Moderator
Posts: 1273
Joined: Wed Sep 12, 2007 12:49 pm

#2

Postby Jon » Fri Feb 24, 2017 12:50 pm

Backslash (\) is probably invalid in a URL, can you change it to a forward slash?
0 x

neilnewman
Ebase User
Posts: 162
Joined: Fri Dec 20, 2013 1:29 pm
Location: Dartford Borough Council
Contact:

#3

Postby neilnewman » Fri Feb 24, 2017 1:28 pm

Thanks for the reply Jon,
I presume this is some kind of Tomcat security tightening with the latest version 7.0.75.
I will try and get the / replaced by another more suitable character for a URL and give it another test, however this aspx code was not written by me, so it may take a few days.
I will post the outcome here
0 x


Who is online

Users browsing this forum: No registered users and 1 guest