HTTP ERROR 403

[ranochigo]

I've been getting a bunch of error 403 when opening the pages in a new tab. I've tried clearing cache and it still persists. Is it a forum-wide issue or is it just me?

[tranthidung]

I've been getting a bunch of error 403 when opening the pages in a new tab. I've tried clearing cache and it still persists. Is it a forum-wide issue or is it just me?

403s error, do you mean this? It comes from today technical fix from theymos.

• Small bug with the highlighting of forum subjects/thread titles
• What's happening? A forum bug?. Today, the fix from theymos caused the 403s error.

It's annoying that browsers are doing this prefetching without any way for sites to signal that they shouldn't, but it's even more annoying that each browser has a separate way of indicating it via headers, and it's all very poorly-documented. In the case of Opera and apparently some versions of Safari, it seems that a prefetching request can be identified if it has a Sec-Fetch-Dest header but does not have a Sec-Fetch-User header. Bitcointalk.org blocks such requests now. (If anyone starts seeing random 403s, this may be the cause; let me know right away in that case.)

[bL4nkcode]

I experienced it earlier and even now when accessing this thread from email notification and works after I refresh a few times.

[ranochigo]

403s error, do you mean this?

Oh I see. I didn't notice that. Yep, that's probably it.

I experienced it earlier and even now when accessing this thread from email notification and works after I refresh a few times.

Only happens when you're opening the link in a new tab. Refreshing the new tab solves the problem.


Broke the merit extension that I'm using too but it's no big deal.

[jackg]

I've experienced nothing of the sort on Firefox (as stated above it looks to just be Safari and Opera) I'd consider moving over to Firefox if the error gets annoying.

[ranochigo]

I've experienced nothing of the sort on Firefox (as stated above it looks to just be Safari and Opera) I'd consider moving over to Firefox if the error gets annoying.

Using Chrome. Yeah, doesn't look to be affecting Firefox.

[theymos]

Fixed, thanks.