You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my specific use case there is a custom header that contains url-like data (server side). The decoding makes hardly possible the further processing of the data.
What do you thing about adding some flexibility to the function? Suggestions:
global or server-level option to disable the url decoding;
configurable set of headers that can be excluded from decoding.
The text was updated successfully, but these errors were encountered:
I am ok with "global or server-level option to disable the url decoding". If we take this option, are there any possible side effects that you can think of? Thanks!
Hi @yhirose
While parsing HTTP headers the library unconditionally applies an url decoding to all headers except for the Location header.
https://github.com/yhirose/cpp-httplib/blob/master/httplib.h#L3809
In my specific use case there is a custom header that contains url-like data (server side). The decoding makes hardly possible the further processing of the data.
What do you thing about adding some flexibility to the function? Suggestions:
The text was updated successfully, but these errors were encountered: