You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using has_redirect_location I found it unexpected that I got a negative result while using it on a response which did have a Location header.
One could ask the general question whether this method should exclude status codes at all or simply look at the existence of a Location header instead (and ignore the status code). However, I'd like to propose to add at least 201 and 202 to the list of commonly redirected status codes since their responses often include them.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When using
has_redirect_location
I found it unexpected that I got a negative result while using it on a response which did have aLocation
header.One could ask the general question whether this method should exclude status codes at all or simply look at the existence of a
Location
header instead (and ignore the status code). However, I'd like to propose to add at least 201 and 202 to the list of commonly redirected status codes since their responses often include them.In case of agreement I have a PR pending.
Beta Was this translation helpful? Give feedback.
All reactions