Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Blocked from site...
- Thread starter icanhazmac
- Start date
- Sort by reaction score
Not sure if it's directly related to your issue, but I've been unable to pull the RSS feed since last week. I get a 403 (Forbidden) error in my feed reader, meaning blocked. Seems to likewise be Cloudflare saying nope to my reader. Not sure what's changed.
I've been seeing this problem sporadically for at least a couple of days.
In one case, it was in a Firefox browser, and it's very much intermittent. My first response was to delete all cookies and quit Firefox, which did fix it temporarily. I later found that simply quitting Firefox and relaunching it would fix it (again, temporarily).
In the other case, it was 100% consistent. It was the 'curl' command-line tool, and it was failing every time with a 403 Forbidden response. My work-around was to use a user-agent string other than "curl/whatever". Even something fanciful, like "Fanciful/99" would cause 'curl' to work.
I retested the aversion to "curl/WHATEVER" by setting Safari's user-agent string to "curl/99", and that led to 100% failures. I also tried some fictional user-agents, like "Bond/007" or "Smart/86", and they worked ok.
In one case, it was in a Firefox browser, and it's very much intermittent. My first response was to delete all cookies and quit Firefox, which did fix it temporarily. I later found that simply quitting Firefox and relaunching it would fix it (again, temporarily).
In the other case, it was 100% consistent. It was the 'curl' command-line tool, and it was failing every time with a 403 Forbidden response. My work-around was to use a user-agent string other than "curl/whatever". Even something fanciful, like "Fanciful/99" would cause 'curl' to work.
I retested the aversion to "curl/WHATEVER" by setting Safari's user-agent string to "curl/99", and that led to 100% failures. I also tried some fictional user-agents, like "Bond/007" or "Smart/86", and they worked ok.
I was doing some testing with 'curl' today, including with a user-agent string of "curl/anything" that was previously failing. This time it worked.
Next I checked it in Safari, using "curl/99", and that worked, too.
It appears that the problem has been corrected, but confirmation from @icanhazmac would be an additional data point.
Next I checked it in Safari, using "curl/99", and that worked, too.
It appears that the problem has been corrected, but confirmation from @icanhazmac would be an additional data point.
It seems the elves who usually fix these technical problems were busy with some annual holiday they were working overtime for, so it took longer than usual for this problem to be put on the work schedule. At least that's what some of the tiny caribou are whispering.