Gustaf, thank you very much. You are amazing as always. I thought "Authorization" is always kind of key -> pair values, guess I was wrong. I think most of them are so.
Thank you. On Sat, Nov 21, 2020 at 7:05 PM Gustaf Neumann <neum...@wu.ac.at> wrote: > Dear Maksym, > > [ns_conn auth] handles Digest authentication (i've never used it), but > "Bearer" is not handled. > The fields in the "Authorization" request header field are not always > structured the same way, > so NaviServer tries it interprete it based on the first word. The known > types are enumerated > in the C code. > > I've added a sensible result for the "Bearer" Authorization to bitbucket. > > all the best -g > > > > On 21.11.20 17:59, Maksym Zinchenko wrote: > > Hello, hope you are doing well. > I have a little question. Maybe a bug, would be so kind to help me out. > According to documentation [ns_conn auth] should return all authorization > headers as a ns_set. > It works fine when using "Basic Authentication scheme", i've seen in the > source code it should work with "Digest" > But when im trying to use "Bearer Authentication scheme" or "Custom" it > returns empty ns_set, but i can see Authentication part in [ns_conn > headers]. > > P.S. > Im using https://reqbin.com/ to test my API request. > > Thank you > > > _______________________________________________ > naviserver-devel mailing > listnaviserver-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/naviserver-devel > > _______________________________________________ > naviserver-devel mailing list > naviserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/naviserver-devel >
_______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
