-
Notifications
You must be signed in to change notification settings - Fork 722
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
Specific to Microsoft Graph (service providers): Re-ordered URL Query Params causes trouble #123
Comments
@olihey sorry to hear that. Thank you for sharing your experience. Technically To bring better experience; let me have a look and get back to you. |
@olihey I have done my analyzes. As you know per RFC there is no order preserve requirement. Also standard package url.Values.Encode(...) sorts query params alphabetically. To bring balance and better resty user experience. I have enhanced the resty to preserve query string order partially, it means "resty will preserve query string order on provided URL not on Please give it try and share your feedback. Then it will be part of |
The fix works for me. Thanks a lot 👍 If you don't see any issue in merging the changes you made, then please go for it. |
@olihey Thanks I'm glad to merge this enhancement. It is fully compatible with RFC and previous resty versions too. |
Great, thanks again for the quick help! |
Merged 😄 |
Hej,
I am working with Microsoft Graph and resty. Awesome so far but now I ran into an issue. I get download / upload URLs from the API and using them with resty always fails. The reason is that resty reorders the URLs query parameters.
For example this is the URL I get from Microsoft:
but resty finally sends the following:
I know that "technically" those two URLs express the same but the Microsoft Graph API seems to be picky about them. So after some debugging I found out that I can make this work with resty when I remove the
parseRequestURL
from thebeforeRequest
list.Any chance we can make this an option? There is already an
SetDoNotParseResponse
. I am happy to contribute aSetDoNotParseRequestURL
as PR. Would that be okay?The text was updated successfully, but these errors were encountered: