Saleem,

On Tue, Nov 6, 2012 at 8:56 AM, saleem <asaleemud...@cdac.in> wrote:

>  Thanks for the quick response ,
>
> i tried to modify bit of xml.py file though i am new bee to python , what
> i tried to do was so filter based on the pattern (<!) .
>

That doesn't make much sense, simply comment the lines where we're taking
the request/response and writing it to the XML.


>
> but when i tried to execute w3af script i am getting error like :
>
> *Error while reading plugin options.
> Error while loading plugin "plugins.output.xmlFile". Exception: unexpected
> indent (xmlFile.py, line 270)*
>

Your plugin modification is incorrect, please verify that your code is
properly indented (indentations should be 4-spaces, not tabs)


>
> I have attached a screen shot of the code that i tried to modify , please
> help me in solving this issue .
>
> Thanks & regards ,
> saleem
>
>
>
> On Monday 05 November 2012 06:08 PM, Andres Riancho wrote:
>
> Saleem,
>
>     The only way to avoid those HTTP requests and responses to appear in
> the XML is to modify the xmlFile.py source code. We don't have any
> configuration options to disable this and I don't believe it would add much
> value to add it myself. If you want to do it, please go ahead and send us
> the patch for review :)
>
> Regards,
>
> On Mon, Nov 5, 2012 at 2:46 AM, saleem <asaleemud...@cdac.in> wrote:
>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>   Hi w3af,
>>
>>  I am generating output in XML format and it is working very fine , but
>> that file is getting huge because of html content , which is getting
>> appended in the HTTP response header , can u please tell me procedure so
>> that i have only request and response headers in the output xml file . I am
>> attaching a screen shot , please help me out .
>> Thanks & regards ,
>> Saleem
>>
>>
>>
>>
>>
>>
>> -------------------------------------------------------------------------------------------------------------------------------
>>
>> This e-mail is for the sole use of the intended recipient(s) and may
>> contain confidential and privileged information. If you are not the
>> intended recipient, please contact the sender by reply e-mail and destroy
>> all copies and the original message. Any unauthorized review, use,
>> disclosure, dissemination, forwarding, printing or copying of this email
>> is strictly prohibited and appropriate legal action will be taken.
>> -------------------------------------------------------------------------------------------------------------------------------
>>
>>
>
>
>
> --
> Andrés Riancho
> Project Leader at w3af - http://w3af.org/
> Web Application Attack and Audit Framework
> Twitter: @w3af
> GPG: 0x93C344F3
>
>
>
> -------------------------------------------------------------------------------------------------------------------------------
>
> This e-mail is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies and the original message. Any unauthorized review, use,
> disclosure, dissemination, forwarding, printing or copying of this email
> is strictly prohibited and appropriate legal action will be taken.
> -------------------------------------------------------------------------------------------------------------------------------
>
>



-- 
Andrés Riancho
Project Leader at w3af - http://w3af.org/
Web Application Attack and Audit Framework
Twitter: @w3af
GPG: 0x93C344F3
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
W3af-develop mailing list
W3af-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/w3af-develop

Reply via email to