hi Steven.
find it "patched" with the last commit.
kr
On Wed, Jun 22, 2011 at 4:27 AM, Steven Pinkham wrote:
> Miroslav Stampar wrote:
>> p.s.
>>
>> with the last update (r4153) only run with non-80 ports will result in
>> :port scheme (which is comformant to
>> http://www.w3.org/Protocols/rfc2
Miroslav Stampar wrote:
> p.s.
>
> with the last update (r4153) only run with non-80 ports will result in
> :port scheme (which is comformant to
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html).
>
> this should be the best way to solve this issue.
>
> thank you for your report
>
> kr
p.s.
with the last update (r4153) only run with non-80 ports will result in
:port scheme (which is comformant to
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html).
this should be the best way to solve this issue.
thank you for your report
kr
On Tue, Jun 21, 2011 at 10:48 PM, Miroslav Sta
hi David.
it should be "patched" with the latest commit.
thing is that some web servers don't act good with Host:port scheme,
hence the behavior you've noticed. this is prone to changes and we are
opened for suggestions.
kr
On Tue, Jun 21, 2011 at 10:39 PM, David Rhoades
wrote:
> I'm using sql
I'm using sqlmap/1.0-dev (r4149).
The HTTP Host header is missing the port number when the target is on a
non-standard port, such as http://target:8080.
Here is an example targeting OWASP's Insecure Web App
(https://www.owasp.org/index.php/Category:OWASP_Insecure_Web_App_Project).
$ ./sqlmap.py
