I am magically unable to reproduce this at the moment.
If I end up seeing the behavior again, I will get more information to reproduce
with.
However, I did realize that I no longer actually need —skip-urlencode. At some
point between when I last touched this code and now, POST request bodies ar
Either through request file or headers. Otherwise, sqlmap automatically
sets it based on recognized type (e.g. application/json for JSON)
Bye
On Oct 19, 2015 7:05 PM, "Brandon Perry" wrote:
> Just curious, how do you expect a user to set a specific content type? Is
> there are argument I am miss
Just curious, how do you expect a user to set a specific content type? Is
there are argument I am missing, or is --headers the expected way?
On Mon, Oct 19, 2015 at 9:41 AM, Miroslav Stampar <
miroslav.stam...@gmail.com> wrote:
> I really can't enforce this behavior. Waiting for your sample.
>
>
I really can't enforce this behavior. Waiting for your sample.
Bye
On Mon, Oct 19, 2015 at 4:04 PM, Brandon Perry
wrote:
> Yes, I can, but it will have to be when I get home this evening.
>
> FWIW, I am interacting with the sqlmap API, so not passing it a request
> file. I am building the SOAP
Yes, I can, but it will have to be when I get home this evening.
FWIW, I am interacting with the sqlmap API, so not passing it a request
file. I am building the SOAP XML programmatically, then setting it as the
'data' in the options (along with headers to specify text/xml and
SOAPAction), with ski
Hi.
But sqlmap should automatically skip the url encoding of such request
bodies if the content-type has been set to the proper value from start (or
if there was no content-type from the beginning).
Can you please send a sample request file and/or used sqlmap options.
Bye
On Mon, Oct 19, 2015 a
The actual request is a SOAP payload, which requires a content type of XML,
and no URL encoding (which, if performed, returns a 50x).
On Mon, Oct 19, 2015 at 6:37 AM, Miroslav Stampar <
miroslav.stam...@gmail.com> wrote:
> Hi Brandon.
>
> Sorry for late reply. It goes like this.
>
> Your header v
Hi Brandon.
Sorry for late reply. It goes like this.
Your header value for content-type should be propagated/used, even in this
case, in all cases THAN one.
If you use --skip-urlencode and you (or your request file) state that the
content-type should be "urlencoded" sqlmap forces switch to eithe
