-
Notifications
You must be signed in to change notification settings - Fork 112
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 307 and 308 status codes are not treated as redirects #147
Comments
Hello @BigstickCarpet, thanks for your issue. It seems reasonable to me that It looks like you already know where to fix that, would you like to make a PR? |
Ok, I'll submit a PR when I get a free moment. May not be for a few weeks though, because I'm about to leave for vacation |
but the commit is right there! 😨 |
hahaha... gotta fork the repo, checkout, branch, commit, test, open a PR... Ain't nobody got time for that! 😸 |
Added PR #154 with @BigstickCarpet 's change. Thanks all this was a blocker for us too :D |
add 307,308 to redirect assertion #147
Closed by #154 |
Not sure if this is by design or not, but the
.redirect
and.redirectTo
assertions currently only test for 301, 302, and 303 status codes. Shouldn't this list also include HTTP 307 (Temporary redirect) and HTTP 308 (Permanent redirect)?The text was updated successfully, but these errors were encountered: