Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

http://google.com/ will NEVER respond with 200 OK #111

Open
Kwpolska opened this issue Jan 20, 2015 · 2 comments
Open

http://google.com/ will NEVER respond with 200 OK #111

Kwpolska opened this issue Jan 20, 2015 · 2 comments

Comments

@Kwpolska
Copy link

Instead, http://google.com/ will respond with 302 Found, then redirecting to http://www.google.XX?gfe_rd=cr&ei=YYYY, where XX is the ccTLD appropriate for the user’s location and YYYY is some magic cookie.

If you use http://google.com/ncr (no country redirect), it will respond with 301 Moved Permanently, then redirecting to http://www.google.com/ncr.

That’s pedantry, but that’s what you get for wasting half the document explaining keyboards, which is not the point of this question.

@kojiromike
Copy link

Preceded by #88

@Petah
Copy link

Petah commented Jan 20, 2015

which is not the point of this question

What is the point of this question? I thought it was to explain everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants