Getting a Browser "Bad Request" Notice When Navigating MyGolfSpy

[Golf2Much]

Lately, when I hit the browser back arrow or move between MyGolfSpy pages I get this:  a white screen and

"Bad Request

Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.

Additionally, a 400 Bad Request error was encountered while trying to use an ErrorDocument to handle the request."

I'm using MS Edge.  I don't seem to have this issue with other sites I visit.   I've checked the solutions online and they all seem to lean towards the cookies being too big to load.  I've their suggested solution of deleting cookies for the site, but that doesn't seem to work.

Anyone else having this issue?  I never had it before, but I think MS Edge was recently just updated.

Thank you in advance.

[Stuka44]

Yes I  also just began receiving the same message, likewise for on-line suggestions to eliminate.  I first thought it was old computer at office.  but now getting same message on newer laptop that I otherwise had not problems with...

On 3/3/2023 at 9:28 AM, Golf2Much said:

"Bad Request

 

[GolfSpy_APH]

53 minutes ago, stuka44 said:

Yes I  also just began receiving the same message, likewise for on-line suggestions to eliminate.  I first thought it was old computer at office.  but now getting same message on newer laptop that I otherwise had not problems with...

 

Apologies for seeing this late. 

I don't see or can replicate, however try clearing your cache. When that has happened to me in the past this has resolved it 

Let me know!

[Golf2Much]

It must be something to do with MS Edge browser.  I downloaded and did some MyGolfSpy surfing and had no issues. 

I've tried clearing the cookies and cache.  It worked for a while, then reared it's ugly head again.

[Larryw]

On 3/3/2023 at 8:28 AM, Golf2Much said:

Lately, when I hit the browser back arrow or move between MyGolfSpy pages I get this:  a white screen and

"Bad Request

Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.

Additionally, a 400 Bad Request error was encountered while trying to use an ErrorDocument to handle the request."

I have been getting this same error using Chrome browser for the past week or so. Never ocurred prior to that.

Not every time but once it occurs it is consistent. Not sure if it is a new security feature of Chrome or possibly a cookie storage issue? Or possibly if some  loading/tracking data is being tacked onto the end of Chrome's request resulting in excessive length. Once it occurs then the back button, reload button load more activity button all seem to fail.

I closed site and reopened but the issue was still occuring. Went to Edge browser and could not duplicate issue. Reopened Chrome browser and issue has not reoccured today. Will try to do some more isolation testing next time it occurs.

I read the forum using the "unread content" method so possibly it is related to the "paging" code? It occurs when opening a thread in a new page (to read) and sometimes when clicking on the "load more activity" tab at the bottom of the thread listing.

[GolfSpy_APH]

2 hours ago, Larryw said:

I have been getting this same error using Chrome browser for the past week or so. Never ocurred prior to that.

Not every time but once it occurs it is consistent. Not sure if it is a new security feature of Chrome or possibly a cookie storage issue? Or possibly if some  loading/tracking data is being tacked onto the end of Chrome's request resulting in excessive length. Once it occurs then the back button, reload button load more activity button all seem to fail.

I closed site and reopened but the issue was still occuring. Went to Edge browser and could not duplicate issue. Reopened Chrome browser and issue has not reoccured today. Will try to do some more isolation testing next time it occurs.

I read the forum using the "unread content" method so possibly it is related to the "paging" code? It occurs when opening a thread in a new page (to read) and sometimes when clicking on the "load more activity" tab at the bottom of the thread listing.

Normally if this happens a simple cache clear will sort it all away. 

[Golf2Much]

I cleared the cache and was responding that I've had the same issue in both Chrome and MS Edge when it popped up again.  For some reason, I'm having issues being able to stay on the site.

[GolfSpy_APH]

44 minutes ago, Golf2Much said:

I cleared the cache and was responding that I've had the same issue in both Chrome and MS Edge when it popped up again.  For some reason, I'm having issues being able to stay on the site.

Are you able to send screenshots here or via PM?

[Larryw]

2 hours ago, GolfSpy_APH said:

Normally if this happens a simple cache clear will sort it all away. 

Just occurred again today (Chrome browser) - when the 404 occurs, reloading the MGS website does not clear the issue. Closing and relaunching the browser does seem to clear the issue.

So clearing the cache is probably restoring operation. However, that may be fixing the symptom and  not addressing the cause of cache needing to be cleared.

Assumption since the issue occurs again at a later time. Something is causing the cache coruption.

[GolfSpy_APH]

1 hour ago, Larryw said:

Just occurred again today (Chrome browser) - when the 404 occurs, reloading the MGS website does not clear the issue. Closing and relaunching the browser does seem to clear the issue.

So clearing the cache is probably restoring operation. However, that may be fixing the symptom and  not addressing the cause of cache needing to be cleared.

Assumption since the issue occurs again at a later time. Something is causing the cache coruption.

I had a similar issue where this occurred quite often, however this has not been the cause for a while now. 

Regardless we will look into it and see if there is anything wonky on our end. 

[Golf2Much]

Here's the white screen with black letter message:

"Bad Request

Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.

Additionally, a 400 Bad Request error was encountered while trying to use an ErrorDocument to handle the request."

This is the page source:  

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<html><head>

<title>400 Bad Request</title>

</head><body>

<h1>Bad Request</h1>

<p>Your browser sent a request that this server could not understand.<br />

Size of a request header field exceeds server limit.</p>

<p>Additionally, a 400 Bad Request

error was encountered while trying to use an ErrorDocument to handle the request.</p>

</body></html>

 

[Fred Mitchell]

I have a new and fairly stout computer and I get it in microsoft edge some days also

 

[GolfSpy_APH]

29 minutes ago, Fred Mitchell said:

I have a new and fairly stout computer and I get it in microsoft edge some days also

 

There were a few updates which were run and should have taken care of these issues. 

 

 

 

[Larryw]

Still happening to me today. Both Chrome and Edge.

In doing a little testing to try to isolate issue noticed that if I use the navigation trail at the top of the pages, issue seems not to occur. More testing needed to confirm but seems to be the trend.

My normal usage pattern is to use the "unread content" link at the top right of the page - after a few page loads the error occurs. Now, I do load each unread topic(that I want to read) by right clicking on the small icon next to the topic title that opens the first unread posting and I open it in a new tab. After reading the unread portion of the thread - I then close the tab, returning focus to the previous tab - which is still displaying the unread content listing.

Not always on the first new tab but after the first few new tab openings, the 404 error occurs. Clearing site cookies will fix the issue. Just guessing but appears that setting navigation cookies on new tab and then returning to previous tab is the common trigger mechanism.

Or maybe not.

[GolfSpy_APH]

10 hours ago, Larryw said:

Still happening to me today. Both Chrome and Edge.

In doing a little testing to try to isolate issue noticed that if I use the navigation trail at the top of the pages, issue seems not to occur. More testing needed to confirm but seems to be the trend.

My normal usage pattern is to use the "unread content" link at the top right of the page - after a few page loads the error occurs. Now, I do load each unread topic(that I want to read) by right clicking on the small icon next to the topic title that opens the first unread posting and I open it in a new tab. After reading the unread portion of the thread - I then close the tab, returning focus to the previous tab - which is still displaying the unread content listing.

Not always on the first new tab but after the first few new tab openings, the 404 error occurs. Clearing site cookies will fix the issue. Just guessing but appears that setting navigation cookies on new tab and then returning to previous tab is the common trigger mechanism.

Or maybe not.

Will continue to look into it. I solely use Recent Content/unread content and haven't been able to replicate the same issue on multiple devices and browsers. 

That being said will still check it out. I know header size was an issue, however that was resolved by reducing it.

I'll double check the theme settings and others, hopefully find a resolution for you.

[berkeleybob]

I’ve started running into this sort of issue lately as well.

I’m on a iPad Pro, Safari browser.

I’ll have the forum up on one of my tabs.

I’ll notice a number next to the tab’s name for notifications.

I’ll go to that tab and tap on the notification bell.

The dropdown list shows, I’ll click on one of the items, and this shows up:

I know I have internet because other tabs, email and other apps will work fine. I’ll reload/refresh and then the page I want appears.

[Golf2Much]

I've had better luck over the last several days.  No longer getting the "Bad Request" white screen.  I did go into my MS Edge Settings, clicked Privacy, Search and Services, click "Clear browsing data now" (choose what to clear) and clicked Time Range "All Time".  I had to log into MyGolfSpy after, but I don't get the "Bad Request" any longer. 

[Larryw]

So, I read the forum today for about 30 minutes staying in the menu bread crumbs trail at the top of the page and read probably 20 threads at random with no issues.

I then clicked on the "unread content" link and without reading any threads scrolled to the bottom of the page and clicked on the "load more activity" button. Immediately the "site error" popup appeared and was not able to recover with any navigation methods. Back button or reload and even load the site totally new in the browser - nothing worked. Closing the browser and reopening the browser did work to allow MGS site to be loaded again.

This is a navigation issue that I cannot overcome. Clearing cookies fixes it but will occur again almost immediately reading forum using unread content.

I will use the bread crumbs one more time for a longer period to insure that it is just an unread content paging/navigation issue but reading the entire forum using just the bread crumbs is not enjoyable.

[GolfSpy_APH]

1 hour ago, Larryw said:

So, I read the forum today for about 30 minutes staying in the menu bread crumbs trail at the top of the page and read probably 20 threads at random with no issues.

I then clicked on the "unread content" link and without reading any threads scrolled to the bottom of the page and clicked on the "load more activity" button. Immediately the "site error" popup appeared and was not able to recover with any navigation methods. Back button or reload and even load the site totally new in the browser - nothing worked. Closing the browser and reopening the browser did work to allow MGS site to be loaded again.

This is a navigation issue that I cannot overcome. Clearing cookies fixes it but will occur again almost immediately reading forum using unread content.

I will use the bread crumbs one more time for a longer period to insure that it is just an unread content paging/navigation issue but reading the entire forum using just the bread crumbs is not enjoyable.

Unfortunately I haven't been able to replicate the issue and have tried copying what you are doing. 

I will continue to as well, but not sure where the issue is as it seems isolated to yourself and a small handful of others that have reported it.