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
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.
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.
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
The text was updated successfully, but these errors were encountered: