Can the Origin header have alphabetical port or parameters in a real-life scenario?

I’m testing this application which is properly validating origin header on the sever side. However, if I add any domain and the expect domain as port, application still consider this valid.
Origin: https://random-domain.com:expected-domain… Continue reading Can the Origin header have alphabetical port or parameters in a real-life scenario?

This application is not using CSRF token but they are still able to protect sensitive actions on the site

This application is not using any CSRF token and not even cookies to identify users on their server. All they do is use a authorization header to identify users. Since an attacker doesn’t know value of this header he can’t send cross site … Continue reading This application is not using CSRF token but they are still able to protect sensitive actions on the site