We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using an old, probably misconfigured, SOAP service running on PHP.
Currently, the call fails due to a 406 error. I identified (reproducing with curl) that the problem is the Accept header.
When defaulted to "/" by curl, it works. But gosoap enforces it to "text/xml" and in this case it fails.
Is it possible to evolve gosoap to offer a control over this header? I can do the change and propose a PR if you agree.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm using an old, probably misconfigured, SOAP service running on PHP.
Currently, the call fails due to a 406 error. I identified (reproducing with curl) that the problem is the Accept header.
When defaulted to "/" by curl, it works. But gosoap enforces it to "text/xml" and in this case it fails.
Is it possible to evolve gosoap to offer a control over this header?
I can do the change and propose a PR if you agree.
The text was updated successfully, but these errors were encountered: