URL Length Limitation
BugImprovement
With recent updates to http request URLs from microsoft, the length of the URLs now exceeds 255 characters. It appears yaak will not accept pasting those in completely, they get cut off.
With recent updates to http request URLs from microsoft, the length of the URLs now exceeds 255 characters. It appears yaak will not accept pasting those in completely, they get cut off.
Sign in to leave a comment.
Can you provide more detail? Where are you pasting them, and what happens to them? (error, truncation, etc)
You can use this endpoint to test POST, should just get a 202-
https://default57be6827a78e4992a0f2edd3e4226e.8f.environment.api.powerplatform.com:443/powerautomate/automations/direct/workflows/cb975241e4734db6ad6e44870bd55ba8/triggers/manual/paths/invoke?api-version=1&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=k-HQLCk7PNDiUhsk8iLYvgjU1udBs5baZ6UQV6flun0
Yes, I get a 202 for this. Is that not correct?
The “truncating” you are seeing, I think, is Yaak importing the querystring parameters. On paste, Yaak extracts the params and puts them into the Params tab for easier editing. All future edits to params should be done in the Params tab.
If you add the params back to the URL but still have them in the Params tab, they will be sent as duplicates. This is potentially why you are seeing the errors?
Let me know if that makes sense.
Ok, yes that would make total sense then. I was expecting to see the entire URL as you do in postman/bruno/others.
Thanks
The new webhook URL format for power platform look something like this- https://default57be6827a78e4992a0f2eddxxxxxx.8f.environment.api.powerplatform.com:443/powerautomate/automations/direct/workflows/c0d14d52a06e434093e82a37xxxxxxxx/triggers/manual/paths/invoke?api-version=1&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=D7HedyTcEjCW_bh-iUtYwOmiJA9Xf0xxxxxxxxxxx
When pasting into yaak, it gets truncated-
Now, if I just copy the remainder of the URL and paste it, or manually type, it will go in. So it seems paste is just limited, the text input is not.
However, and this may or may not be related, but the POST doesn’t go through even though it works in postman.
Changing the API version parameter results in a weird response too, I’ve never experienced this before-
Also, changing the parameter in the param_name:value boxes does not change it in the URL
That got cut off for some reason