curl to http://www.google.com returns 200 but returns 307 on browser

[smc181002]

when recorded the requests on chrome dev tools, first response was 307 response and after the redirect lead to a 200 response

But in the case of curl, it directly returned 200

I think it is because this 307 is a temporary redirect and the response we get from curl is the final response after the redirect
i just want to confirm this
thank you

[dfandrich]

Questions are better asked on the curl mailing list rather than in a Github issue.

On Wed, Aug 25, 2021 at 09:59:53AM -0700, Meher Chaitanya wrote: I think it is because this 307 is a temporary redirect and the response we get from curl is the final response after the redirect

curl won't follow redirects without the -L option. It could be Google is looking at the User-Agent to decide whether to redirect to a more appropriate site depending on the browser, or it could be the browser internally redirecting to the https: version of the site because of HSTS. Enabling HSTS with curl should give similar results.