cloorc commented on issue #5654: URL: https://github.com/apache/apisix/issues/5654#issuecomment-1122183989
> > > > cc @spacewander @membphis, do you have any options about this? > > > > > > > > > People want APISIX to use a specific URL escape rule to solve some edge problems, like whether `<>` should be escaped. However, the escape rule is vary across different platforms. If we follow one of the rules, we need to change the way to escape URL instead of using Nginx's official way. But this change is neither easy nor compatible with the current behavior. > > > > > > It's unfair to ask APISIX to use specific escape rule to solve some edge problems, but how about leaving the original request along with its orignal style and forwarding it to the backend? I think the middle-steps do whatever might be necessary. > > I still cannot agree it, this makes the URI handling more complicated and error-prone. Just like @spacewander said, the URI encoding/decoding rules are not so standard across platforms. Then, why should APISIX decode the encoded-paramters instead of keeping it as origin? APISIX can decode whatever it needed but please pass the original parameters to the backend finally. This is enough. APISIX can just put the original query parameters into somewhere else and get it back before passing them to the backend services. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
