Start a new topic

How to properly set Authorization Header


I am working with a virtual button right now trying to hit a site that's sitting behind an basic auth layer.

When I log into my server log files I am getting a 401 followed by a 404, which tells me that the server responded with a 401 and couldn't find the error response (404) it wanted to serve.

The button log shows a 404.

Is there a way for me to analyse the full request body the button is making against my server?


you can use e.g. to see the request server is making

Just create your own requestbin and use it's URL for your HTTP action, make a test press, and then refresh the page.

best regards,

Tuukka / bttn


is there any possible way to send header parameter with auxiliary http?

e.g., this configuration,

 url1=,param1=a port=1234 method=post

sends param1 with value 'a' as a form parameter, but I need to send something like

 url1= port=1234 method=post header=param1:a

without parameters but adding a header as param1 and value 'a'.

With curl I would do something like:

curl -H 'TestHeaderParam: TestValue' -X POST

you can run this test.


unfortunately the AUX http does not currently have custom headers capability. If you are targeting a local server, maybe you can make a custom endpoint that does not require headers, or have a proxy between bttn and the server handling the requests?

Best regards,

Tuukka / bttn

Hi, We can do that and we are doing it because it is important to us to contact directly our server. Response time is crucial to us. But it would be nice to have the auxiliary http accepting header parameters, because if you need to pass an API key for a REST service this functionality is useless. Have in mind that a key is always passed in the header to be encrypted. Cheers, Almeno.
Login or Signup to post a comment