Classifieds - Bad Request - Request Too Long
Classifieds - Bad Request - Request Too Long
Author
Discussion

jammy_basturd

Original Poster:

29,778 posts

241 months

Wednesday 15th July 2015
quotequote all
Keep getting this error when browsing the classifieds section (using Chrome 43 on Win 8.1). Also stops the AJAX load of results.

Hitting F5/waiting a few minutes usually cures the problem.


Ollie_M

2,268 posts

135 months

Thursday 16th July 2015
quotequote all
Hi Jammy B

I'll go and chat to our tech guys and see if we can figure out what's causing this

PH

RacingPete

9,196 posts

233 months

Thursday 16th July 2015
quotequote all
The browser is sending too much information in the header to our server and it is then rejected it. Now the header information varies from user to user but we will look to see if we can replicate it here.

jammy_basturd

Original Poster:

29,778 posts

241 months

Thursday 16th July 2015
quotequote all
There was one instance where this happened every time. Select Lotus and Jaguar, all models, then Max Price of £5k. Load up the first page of results, then try to go to the second. The second page never loads for me.

Here's a HAR file from Chrome's DevTools: https://gist.github.com/jammy-git/dfd0d7d384a88d95...

RacingPete

9,196 posts

233 months

Thursday 16th July 2015
quotequote all
jammy_basturd said:
There was one instance where this happened every time. Select Lotus and Jaguar, all models, then Max Price of £5k. Load up the first page of results, then try to go to the second. The second page never loads for me.

Here's a HAR file from Chrome's DevTools: https://gist.github.com/jammy-git/dfd0d7d384a88d95...
Very useful... was that HAR from when you had an issue?

MattDell

3,302 posts

184 months

Thursday 16th July 2015
quotequote all
Isn't this the old login cookie issue? A simple clearing of your cookies would fix that.

MattDell

3,302 posts

184 months

Thursday 16th July 2015
quotequote all
Yeah it's the ASPSESSIONID cookie. There are around 60 in your request.

Have a look at the node with {"url": "http://www.pistonheads.com/classifieds/SearchJson"} and you'll see them.

Clear cookies, that will resolve the issue.

cat with a hat

1,488 posts

147 months

Saturday 15th August 2015
quotequote all
You'll find most users won't bother to clear cookies/hard reaload when they see this, they will simply think the website is f**ked. (Me included!)