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. http://requestb.in to see the request bt.tn 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 requestb.in page.
Tuukka / bttn
is there any possible way to send header parameter with auxiliary http?
e.g., this configuration,
url1=184.108.40.206/yourAction.php,param1=a port=1234 method=post
sends param1 with value 'a' as a form parameter, but I need to send something like
url1=220.127.116.11/yourAction.php 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 http://requestb.in/1bht8qq1
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?
Tuukka / bttn