OK, that's the problem. The HTTP Referer doesn't include the domain name. Since we are filtering by domain name, the check fails and the 403 is thrown. According to
RFC 2616:
If the field value is a relative URI, it SHOULD be interpreted relative to the Request-URI. The URI MUST NOT include a fragment.
The problem is that a relative URI (like the one reported by Chrome) does not guarantee that the Referer doesn't just include random garbage instead of an existing resource on your site.
So, maybe I should just remove that option altogether. When I created it, almost two years ago, all browsers would send absolute URIs. Nowadays, it seems that they all send relative URIs, making this feature useless :(
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!