Andres,

I have 2 questions:

1. FuzzableRequest class have 2 vars called _dc and _data. What differences
in purpose and usage of these vars?

     - "_dc" contains the data container. Usually a map that holds
information like this:

         {'a': ['b',] , 'c': ['d',]}

     - "_data" is the string representation of the above:

         a=b&c=d

     The "_dc" has the form of a map with lists as values in order to
support repeated parameter names like "a=b&a=33".

How and when are these things synchronized?
Or we don't need to synchronize it?

2. we have function called uri2url:

def uri2url( url):
...

Why do we suggest that URL == URI - "query string"?

     Are you proposing a parameter name change from url to uri? If so,
I agree. The result would be:
No, I mean that

http://localhost/foo.asp?xx=yy&bb=dd#fragment is URL
and
http://localhost/foo.asp is also URL

by RFC [0]. So why did we call this function URI2URL?
Am I wrong in understanding differences of URL and URI?

Why I asked about it...?=)
Simply I research W3AF Proxy backend and FuzzebleRequest class.
In the last one we have such methods:

    def setURL( self , url ):
        self._url = url.replace(' ', '%20')
        self._uri = self._url

    def setURI( self, uri ):
        self._uri = uri.replace(' ', '%20')
        self._url = uri2url( uri )

Why do we in common use URI in W3AF?
Why not just URLs?

[0] URL http://tools.ietf.org/html/rfc1738
[1] URI http://tools.ietf.org/html/rfc3986

--
Taras
--
"Software is like sex: it's better when it's free.", - Linus Torvalds.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
W3af-develop mailing list
W3af-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/w3af-develop

Reply via email to