The DSL keywords are much more preferable since that allows us to play more with the internals. We assure the DSL will work, but we do not assure the internal objects will stay the same. In this specific case, I see no reason why "request->headers" won't work forever.
It seems like "headers" is only calling "header" again instead of literally calling the "headers". Vincent, would you be able to raise this as a ticket meanwhile so we could address it and you could easily track it? On Fri, Jul 17, 2015 at 9:44 AM, Lennart Hengstmengel <[email protected]> wrote: > Hi Vince, > > Try: > > my $headercontent = request->header('Your-Header-Here'); > > > Kind regards, > Lennart > > > On 17-07-15 03:08, Vincent Freeman wrote: > >> Hi guys, >> >> I'm new to Dancer2 and I'm trying to access an authorization header, >> similar to Github's 'X-Hub-Signature'. >> >> I consulted with >> https://metacpan.org/pod/distribution/Dancer2/lib/Dancer2/Manual.pod#header,it >> says to use 'headers' to "Adds custom headers to responses" and 'header' to >> "adds a custom header to response", but it does not say how to retrieve the >> header information, rather than adding it. >> >> I'm using starman with nginx as the forward proxy. >> >> This is my code for testing header access: >> >> post '//hook' => sub { >> my $hd = header "Content-Type";; >> "Your Headers: [".$hd."]"; >> }; >> When I issue a curl, it returns empty. >> >> What am I doing wrong? >> >> Feedback welcomed and thanked in advance. >> >> Cheers, >> >> Vince. >> _______________________________________________ >> dancer-users mailing list >> [email protected] >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> > _______________________________________________ > dancer-users mailing list > [email protected] > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >
_______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
