Revision history [back]

This could be caused by a variety of reasons, such as:

1. Cookies or authentication: Firefox/Chrome may have stored cookies or authenticated your session, giving you access to the website, while curl does not have this information.

2. User-agent: Firefox/Chrome may have a different user-agent than curl, which could trigger different behavior from the server.

3. Proxy settings: Firefox/Chrome may have proxy settings configured, while curl does not, causing different connectivity and routing paths.

4. Server-side IP detection: The server could be configured to allow only specific IPs or ranges, and Firefox/Chrome may be accessing the website from an allowed IP, while curl is not.

To further investigate, you could try clearing your browser history and cookies and retrying the request in Firefox/Chrome to see if you still get a 200 response. You could also inspect the HTTP response headers from both Firefox/Chrome and curl to look for differences.