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.

Sign up for GitHub

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

Jump to bottom

redirectPort: listener should trigger a 302 redirect #173

Closed
abovedave opened this issue May 30, 2017 · 1 comment
Closed

redirectPort: listener should trigger a 302 redirect #173

abovedave opened this issue May 30, 2017 · 1 comment
Assignees
@abovedave
Labels
type: enhancement

Comments

@abovedave
Copy link
Contributor

abovedave commented May 30, 2017 •
edited
Loading

Currently it sends a 301, I suggest changing this to a 302 so the redirect is not permanently cached - which is a pain when debugging etc.

N.B. research says search engines are indifferent to redirect type.
@abovedave
Copy link
Contributor Author

Related discussion I dug up when looking at multi-lingual redirects: https://moz.com/community/q/language-detection-redirect-301-or-302#reply_162161

abovedave pushed a commit that referenced this issue Jun 1, 2017
feat: change redirect status code #173
3e154a7
@abovedave abovedave mentioned this issue Jun 1, 2017
Closed
6 tasks
abovedave pushed a commit that referenced this issue Jun 2, 2017
fix: update redirect test #173
e1a8abc
abovedave pushed a commit that referenced this issue Jun 2, 2017
fix: update redirect test #173
e21d0eb
@abovedave abovedave mentioned this issue Aug 8, 2017
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@abovedave abovedave

Labels
type: enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@abovedave