-
Notifications
You must be signed in to change notification settings - Fork 563
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
Request parameters encoding doesn't work in v1 of the spec #1279
Comments
Hi there, I was wondering if there's anything we can do to resolve this? Currently this is blocking our testing and release process, and if there's anything we can do to help in this, please let us know. |
Hi @erikpragt-connectid, |
Hi @deki , thanks, I'll do that! |
Hi, @erikpragt-connectid, thanks for raisong the issue. I'll be working on it this sprint. I'll keep you updated on the progress. |
Sorry for the delay, currently working on the issue. I should send a PR by end of day. |
PR out. |
Hi @deki ,
We found another issue, which is related the encoding of parameters. For example, when we send a timestamp, we could send the timestamp either as
time=1970-01-01T00:00:00.004Z
ortime=1970-01-01T00%3A00%3A00.004Z
. When we send this through a Function URL (so, v2 of the spec), all works well, we can call our endpoint using an encoded an un-encoded value.However, when we use the ALB, which used v1, the unencoded version works, but when we encode the parameters, there's an exception in the code:
I have a demo application if you need one, it doesn't do much, except for consuming a request parameter:
The text was updated successfully, but these errors were encountered: