Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 5
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1230 times and has 4 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Website Support: 400 Bad Request, causing posts to fail. - Linux Only!

Without exception, from FireFox 3.6.13 when hitting *reply* or *quick reply* or starting a *new thread* and writing a post, the preview or post fails if the time it took was longer then about 30 seconds. Then the post just sits in the air and the tab turns:

"400 Bad Request"

with the text:

Bad Request

Your browser sent a request that this server could not understand.

Paging back only shows the blank writing area... all text gone. This is quite irritating if forgetting to do the Ctr-A / Ctrl-C before hand.

If previewing a post and again writing or rereading for longer than 30 seconds, the same happens. Back paging then produces the pre-preview text without any edits added, leading to incomplete posts, needing editing again.

Been going for months now and only on Linux. From Windows and FireFox posts go through fine. It's the only installed browser.

thanks

edit: On suggestion of Lawrence, below added platform specificity in title.
----------------------------------------
[Edit 1 times, last edit by Former Member at Feb 13, 2011 3:37:37 PM]
[Feb 13, 2011 2:57:34 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Website Support: 400 Bad Request, causing posts to fail.

This is a 'reply' using Firefox 3.6.13 on Windows 7 64-bit OS after about a minute.

confused

Added: Looks likev we need a Linux Error in the header to attract other Linux users attention.
----------------------------------------
[Edit 1 times, last edit by Former Member at Feb 13, 2011 3:27:00 PM]
[Feb 13, 2011 3:24:59 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Warped@RSA
Senior Cruncher
South Africa
Joined: Jan 15, 2006
Post Count: 440
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Website Support: 400 Bad Request, causing posts to fail.

This is a Quick Reply using Ubuntu 10.04 (Lucid Lynx) 64-bit and Firefox 3.6.13

Preview worked as expected as well.
----------------------------------------
Dave
[Feb 13, 2011 3:40:52 PM]   Link   Report threatening or abusive post: please login first  Go to top 
sk..
Master Cruncher
http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif
Joined: Mar 22, 2007
Post Count: 2324
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Website Support: 400 Bad Request, causing posts to fail.

This might be specific to one or two version of Linux. So you might want to add your OS version to the title. Could this be down to an add-on you are using (Reload Every)?
I did see something like this in the past - very annoying. I guess FF must be refreshing the page every visit, rather than being intelligent about it. So a security timeout/page refresh is occurring every 30sec. Firewall? Is your cache set to 50MB or zero (Tools, Options, Advanced, Network)?
On Vista x64 FF 3.6.13, when I write a reply I sometimes have to log on again. When this happens I also get the 400 Bad Request Error after logging in, but I can go back and copy/paste or just click 'Reply to the post' again.
----------------------------------------
[Edit 2 times, last edit by skgiven at Feb 13, 2011 8:46:56 PM]
[Feb 13, 2011 8:44:11 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Website Support: 400 Bad Request, causing posts to fail.

So far today, not a single post has hung on this time out. Did find that one hit to the WCG forums created some 10 or more cookies, so maybe these were not jiving, though all possible jars were emptied multiple times.

That said, a few add-ons updated in the last day, so maybe it was any of these... No-Script is the most frequently updated, but there were no stop signs from their status icon to indicate something was being held up. Wish i'd remember how to start FireFox temporarily without add'ons... safe mode it was or something.

We'll probably never know.
[Feb 18, 2011 4:38:01 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread