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

Consider using httpparty's maintain_method_across_redirects #41

Open
bbaugher opened this issue Nov 2, 2015 · 2 comments
Open

Consider using httpparty's maintain_method_across_redirects #41

bbaugher opened this issue Nov 2, 2015 · 2 comments

Comments

@bbaugher
Copy link

bbaugher commented Nov 2, 2015

Specified a http URL for our JIRA instance which then later was setup for https and re-directed to that location. In this case I was doing a Jiralicious.search which was now returning all issues for JIRA instead of filtering with my JQL query. Using httpparty debug I found the re-direct was then having httpparty send the POST as a GET which is a different search REST API which doesn't look at the request body for JQL. Using maintain_method_across_redirects should resolve this issue.

httparty (0.11.0)
jiralicious (0.5.0)
JIRA : 6.3.12

@shortdudey123
Copy link
Contributor

Have you verified that the redirect is a 307/308 and not a 301/302?
httparty should be honoring those and if not, a bug should be opened on their side

@dorack
Copy link
Owner

dorack commented Jan 14, 2017

The question is why is httparty doing a redirect? by default the site should not be doing a redirect unless there is another mechanism in place forcing the non-persistent redirection. I would check your configurations ontop of the status codes to validate the state of the system.

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