IMO, problem with immediate table dump after a timeout could be that the
average user would falsely think that everything went ok.
I would really suggest you to find out why all of a sudden the are
timeouts.
Bye
On Jul 15, 2014 12:42 PM, "Dirk Wetter" wrote:
> Hi Miroslav,
>
> Am 07/14/2014 08
Hi Miroslav,
Am 07/14/2014 08:56 PM, schrieb Miroslav Stampar:
> Hi Dirk.
>
> sqlmap doesn't retrieve already retrieved data. It stores them into the local
> session data for later (re)usage.
I thought so too. But when for some reason the network times out or any other
special circumstances occ
ough
> it
> would be great in general if sqlmap would dump the already retrieved data
> if a problem similar to mine occurs.
>
> Cheers, Dirk
>
>
>
>
>
>
> -Original Message-
> From: Dirk Wetter [mailto:s...@drwetter.org ]
> Sent: Monday, July 14, 2014
-
From: Dirk Wetter [mailto:s...@drwetter.org]
Sent: Monday, July 14, 2014 3:13 PM
To: sqlmap-users@lists.sourceforge.net
Subject: [sqlmap-users] dump data after timeout condition
Hi,
sorry if I missed something but wouldn't it make sense to dump already retrieved data if sqlmap is encounter
@lists.sourceforge.net
Subject: [sqlmap-users] dump data after timeout condition
Hi,
sorry if I missed something but wouldn't it make sense to dump already
retrieved data if sqlmap is encountering a timeout beyond the specified/
default value?
[09:54:19] [CRITICAL] unable to connect to the target URL or
Hi,
sorry if I missed something but wouldn't it make sense to dump already
retrieved data if sqlmap is encountering a timeout beyond the specified/
default value?
[09:54:19] [CRITICAL] unable to connect to the target URL or proxy. sqlmap is
going to retry the request
[09:54:20] [CRITICAL] unabl
