Url max length

Status
Not open for further replies.

abcroste

Member
Messages
39
Reaction score
0
Points
6
Hello,

I've got a web service, used by a desktop application to submit bug reports. Everything is passed in the query string when calling the webservice, so the url can several thousand characters long.

Everything used to work fine, but since Thursday 16th October, it seems that URLs that are too long cause an error.

Code:
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at no-reply@x10hosting.com to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

I can't seem to find any logs from cPanel

From my tests, it looks like the url's max length is around 3540 characters.

Can anyone help?


Thanks
 

Dead-i

x10Hosting Support Ninja
Community Support
Messages
6,084
Reaction score
368
Points
83
Hi abcroste,

We recently implemented a different web server setup in our free hosting servers, which is a combination of the Apache web server and the Varnish cache server for fast responses, which may have caused this change. Though we may be able to adjust the URL limit accordingly, I personally would highly discourage sending information such as this in the URL. Might it be better to send your data as a POST request from your application instead? :)

Thank you,
 

AngusThermopyle

Active Member
Messages
319
Reaction score
52
Points
28
Odd.
Was getting the same thing on x02. ~4000 chars threw an error. Now it doesn't

10000 chars gave and still gives a different error, 414 Request-URI Too Long
 

abcroste

Member
Messages
39
Reaction score
0
Points
6
Hi abcroste,

We recently implemented a different web server setup in our free hosting servers, which is a combination of the Apache web server and the Varnish cache server for fast responses, which may have caused this change. Though we may be able to adjust the URL limit accordingly, I personally would highly discourage sending information such as this in the URL. Might it be better to send your data as a POST request from your application instead? :)

Thank you,

Thanks Dead-i,

I'm going to change the way the webservice works so that future versions of the desktop app send data as a POST requests (I never realised before that the data could be so long) but in the meantime can the character limit be set back to the old value? Unfortunately it'll take time before I release a new version of the app, and it'll take a while for all users to upgrade
 
Status
Not open for further replies.
Top