tdp_org, to webdev
@tdp_org@mastodon.social avatar

I made a change on our NEL/Reporting API report collector earlier which changed the response status from 500 to 403 when the client fails to send a valid/any Origin request header on the POST.

This caused a ~2x increase in reports.
(ignore the spikes, they're known)

I then changed the response from 403 to 201 and the reports returned to their previous level. No other changes were made.

Anyone know why this'd be? Would browsers retry on 403?

metabelgica, to Belgium
@metabelgica@fedihum.org avatar

Hello 👋

we are four Belgian Federal Scientific Institutes that want to share FAIR data about Entities related to Belgian Cultural Heritage by the end of 2026.

Here you will find multilingual updates on our project!

More Info
➡️ https://www.kbr.be/en/projects/metabelgica/
➡️ https://github.com/metabelgica
➡️ https://zenodo.org/communities/metabelgica

📣 Please spread the word and follow us!

tdp_org, to webdev
@tdp_org@mastodon.social avatar

In NEL (Network Error Logging) - does anyone know if implementations (so Chrome, mainly) include reporting http.response.redirect_loop ?

I know we definitely have some redirect loops (just found 65 of them via a script) but I am not seeing any reports at all for them in this month's NEL data.

I'd love to have a report of redirect loops driven from NEL data so we can alert on them and get them fixed.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • kavyap
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • InstantRegret
  • Durango
  • Youngstown
  • everett
  • slotface
  • rosin
  • cubers
  • mdbf
  • ngwrru68w68
  • anitta
  • GTA5RPClips
  • cisconetworking
  • osvaldo12
  • ethstaker
  • Leos
  • khanakhh
  • normalnudes
  • tester
  • modclub
  • tacticalgear
  • megavids
  • provamag3
  • lostlight
  • All magazines