Skip to content

Instantly share code, notes, and snippets.

View LanZeroth's full-sized avatar
🏴
Security is an Illusion

Abdullah Shittu aka LegaciesofLekan LanZeroth

🏴
Security is an Illusion
View GitHub Profile
Hi Godfather Orwa, hope you’re doing well.
I’m Abdullah, a cybersecurity researcher and student from Nigeria. I’ve been following some of your work in the cybersecurity community and thought I should reach out.
I’m currently looking forward to GISEC 2026 and hoping to attend this time. Would be great to connect with you and maybe get some advice from you about it.
We couldn’t find that file to show.
@LanZeroth
LanZeroth / null-origin-exp.md
Last active January 14, 2025 09:46
Explanation of null Origin Header in Various Situations

The Origin header in HTTP requests indicates the origin (protocol, host, and port) of the initiating request. However, there are certain situations where the value of this header is set to null. Here's an explanation of the scenarios:

  1. Cross-Origin Redirects

    When a request follows a redirect from a cross-origin domain, the browser may not have a clear origin to attach to the subsequent request. Example: Request is initiated from https://site-a.com and redirects to https://site-b.com. In some cases, after the redirection, the Origin header is set to null to indicate that the origin information is not forwarded.