Re^2: REST::Client does not provide any output (debugging x-authorization)

The actual is "x-appname-Authorization". I removed the appname from the string as it is our application code name which is still under development. Thanks for your time.

Comment on Re^2: REST::Client does not provide any output (debugging x-authorization)

Replies are listed 'Best First'.
Re^3: REST::Client does not provide any output (protocol) by Anonymous Monk on Jun 17, 2013 at 09:24 UTC
The actual is "x-appname-Authorization". I removed the appname from the string as it is our application code name which is still under development. Thanks for your time. Ok, but that still doesn't explain what protocol what rfc that x-authorization header is supposed to follow X- means non-standard , application specific , it doesn't explain what application, what protocol, what format I don't know how curl determines this, but I imagine if you turned on more debugging/verbosity in curl you might find out	[reply]

Replies are listed 'Best First'.

Re^3: REST::Client does not provide any output (protocol)
by Anonymous Monk on Jun 17, 2013 at 09:24 UTC

The actual is "x-appname-Authorization". I removed the appname from the string as it is our application code name which is still under development. Thanks for your time.

Ok, but that still doesn't explain what protocol what rfc that x-authorization header is supposed to follow

X- means non-standard , application specific , it doesn't explain what application, what protocol, what format

I don't know how curl determines this, but I imagine if you turned on more debugging/verbosity in curl you might find out

[reply]