-
-
Notifications
You must be signed in to change notification settings - Fork 853
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
Certain endpoints like resolution
are returning 406 due to invalid accept headers
#1775
Comments
same as #1774 |
You should be able to workaround the issue by creating JIRA client instances like so -> JIRA(url_to_jira_instance, basic_auth=("example", "apikeyhere"),
options={"headers": {"Accept": "application/json,*/*;q=0.9"}}) |
This is exactly what I did, but it required updating a bunch of apps and frameworks that define the JIRA URL, and since |
It looks like Atlassian made the same change in the server info endpoint last night causing the same 406's on just creating a client at all. Would be really nice to have the header fix merged in |
Bug summary
Accept headers defined here: https://github.com/pycontribs/jira/blob/7846ac35a7e219dd3c1cd616a120a920f112b85e/jira/resilientsession.py#L145C9-L146C70
Seem to be invalid, because it should not be
*.*
but*/*
. I'm not sure if the bitbucket bug is still valid, can't open it.As for the other one, it seems changing accept headers to
"application/json;q=1.0, */*;q=0.9"
won't break anything.Is there an existing issue for this?
Jira Instance type
Jira Cloud (Hosted by Atlassian)
Jira instance version
No response
jira-python version
main
Python Interpreter version
3.11.1
Which operating systems have you used?
Reproduction steps
Expected behaviour
200 response
Additional Context
No response
The text was updated successfully, but these errors were encountered: