Resolved Content-Length issue when posting to API endpoint with empty… #73
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@ted-spence-avalara This failed CI but I'm not so sure it was due to my changes, the output seems to suggest a problem with the environment? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have found that several endpoints of the Rest API return LengthRequired along with the following HTTP
`
<TITLE>Length Required</TITLE>Length Required
HTTP Error 411. The request must be chunked or have a content length.
` This seems to be caused by sending a post request with no Content Length header. This appears to happen when the SDK calls a post request and no content is defined. The solution I came up with was to set a manual default value of zero on the ContentLength property (instead of relying on the compiler default).This change should also resolve an open support case that I have. The case number is 15879211.