What in the 9 heck's has been going on here Muhammad?!?

[aczlan]

Generally a 403 often recurs because of a cached page...but the actual error that originally caused the 403 is on the server side not the user side...That's why clearing the cache etc often will solve the current problem...but it does nothing to actually fix the problem that caused the server to throw the error in the first place...

In my case, they started after the DNS got messed up, then fixed, so I suspect that the (outdated) cached page (or cookie, or file) that my browser was using was pointing to a file or server that was no longer accessible.
Once I cleared out the cookies and the cache (1-2 weeks ago?), the 403 errors have not (yet) reoccurred.
As such, I stand by my assertion that something in the cookies or cache on my computer did not match what the server was currently expecting and as such the problem was inside my browser
Now, had the 403 errors continued after clearing the cache and the cookies on my browser, I would agree with you that it was due to a server misconfiguration rather than something wrong with what my browser was requesting.

Aaron Z

 

[bridge4]

Sorry guys, I was asleep during most this last night!

I run an Apple macbook pro with updated OS. and my browser is BRAVE (runs off chrome but MUCH more secure and private). The issue is when I was not logged in, but I found that it was logging me out.

I've cleared my cookies and caches or whatever and that seems to have helped.

That doesn't change the fact that anyone who isn't registered to this site, when visiting, see's an absolutely absurd amount of ads. Like someone said, ads are fine if they aren't out of control and I know they are needed to keep the site up. Moving ads, videos etc... I think that approach is going to make a lot of people look for other options.

 

[pmsmechanic]

For a while I was getting the "403 Access Forbidden" but it's been nonexistent for the last two weeks or so. A simple "reload page" was all it took to resolve the issue. Now I'm having the issue of when I click on the latest post link on my "My Home" page I randomly get taken to the either the first post or somewhere in the middle instead of the last read post. It's a bit annoying but I guess as with all other past issues on this site it will eventually get resolved.

 

[/pine]

In my case, they started after the DNS got messed up, then fixed, so I suspect that the (outdated) cached page (or cookie, or file) that my browser was using was pointing to a file or server that was no longer accessible.
Once I cleared out the cookies and the cache (1-2 weeks ago?), the 403 errors have not (yet) reoccurred.
As such, I stand by my assertion that something in the cookies or cache on my computer did not match what the server was currently expecting and as such the problem was inside my browser
Now, had the 403 errors continued after clearing the cache and the cookies on my browser, I would agree with you that it was due to a server misconfiguration rather than something wrong with what my browser was requesting.

Aaron Z

First you have to understand how the browser/server relationship works...first the browser sends a request to the server for the desired page...A typical modern web page usually has many different files that make up the page...(each image, ad etc is a separate file) on a busy site where the server is constantly filling the requests for a page the server does not always serve the individual files in the same order...
....The different scripts in the page source (sometimes javascript but not always) serve the different ads etc...if the first file served is an ad or other type of "blocked" (by the browser) file it may or may not stop the request and throw an error...the browser recognizes the returning file/page as unique and caches the (new) page which may or may not be an error.

Fewer scripts = fewer errors...

In the case of corrupted DNS caches it is simple to clear the cache...a quick google search will explain the procedure for different O/S's and versions...this is a simple procedure but generally requires entering a command string at the terminal prompt...

 

[PILOON]

"What in the 9 heck's has been going on here Muhammad?"

LOL, Muhammad is in self quarantine mode and bored, so he's making changes for changes sake.

 

[aczlan]

First you have to understand how the browser/server relationship works...first the browser sends a request to the server for the desired page...A typical modern web page usually has many different files that make up the page...(each image, ad etc is a separate file) on a busy site where the server is constantly filling the requests for a page the server does not always serve the individual files in the same order...
....The different scripts in the page source (sometimes javascript but not always) serve the different ads etc...if the first file served is an ad or other type of "blocked" (by the browser) file it may or may not stop the request and throw an error...the browser recognizes the returning file/page as unique and caches the (new) page which may or may not be an error.

Fewer scripts = fewer errors...

In the case of corrupted DNS caches it is simple to clear the cache...a quick google search will explain the procedure for different O/S's and versions...this is a simple procedure but generally requires entering a command string at the terminal prompt...

I understand how the browser server relationship works and how CSS files interact with the HTML and other scripts to change the appearance of the webpage.
My DNS cache wasn't the issue (that was the first thing I cleared after the DNS problems, but I still got 403 errors), clearing the browser cache/cookies got rid of them.

Aaron Z

 

[rekees4300]

Adblock Plus Update: https://new.adblockplus.org/update

 

[Diggin It]

I think somebody hit on the 403 thing over in the Time Warp thread when they made mention that it seems to be related to the mass deletion of posts with the FP purge. That could cause a flubberwaffle in the database and throw any number of errors until cookies and what-nots got caught up again.

 

[California]

I understand how the browser server relationship works and how CSS files interact with the HTML and other scripts to change the appearance of the webpage.
My DNS cache wasn't the issue (that was the first thing I cleared after the DNS problems, but I still got 403 errors), clearing the browser cache/cookies got rid of them.

Aaron Z

That went over my head. I haven't written a web page since back in the day when I used straight HTML for web pages. But ... The add-ons I and others have mentioned should insulate the visitor from the complexity of what's going on, on the other side of the screen. Refreshing cache and cookies at most should be the limit on how deep the reader has to get into the mysteries of modern web fault issues. Looking beyond that, its too easy to get lost down endless rabbitholes.

In my case that was all that was needed to restore flawless function. Hopefully others would get the same results with the same add-ons and maintenance.

 

[5030]

No hits, no runs, no errors. No 403, no adds no videos. Never log out, stay logged in 24/7/365. Don't have a clue what you guys are going thru.

+1 but I will say my ad blocker blocked 18 on this site alone. Only 'pop ups' I like are the strawberry ones with the frosting on them. Site was down for a short yesterday. I figure for an upgrade.

I will 100% be done if he sells out to Vertical Scope. Their websites (there are many VS owned forums) are horrible.