Andres,
> > Now everything looks ok.
> >>>> setParam('http://ya.ru?d=a','aaa')
> > 'http://ya.ru;aaa=?d=a'
>
> Is that valid in RFC?
Hmm, it was a bad example :)
And it looks like it's not valid by RFC [0]
As I understand this RFC path must consist at least 1 symbol:
rel_path = [ path ] [ ";" params ] [ "?" query ]
...
path = fsegment *( "/" segment )
fsegment = 1*pchar
segment = *pchar
...
pchar = uchar | ":" | "@" | "&" | "="
uchar = unreserved | escape
unreserved = alpha | digit | safe | extra
Am I right?
Good example:
>>> setParam('http://ya.ru/q?d=a','aaa=1')
'http://ya.ru/q;aaa=1?d=a'
>>> urlparse('http://ya.ru/q.php;aaa=1?d=a')
('http', 'ya.ru', '/q', 'aaa=1', 'd=a', '')
[0] http://www.isi.edu/in-notes/rfc1808.txt
By the way, it's very strange decision to use such params
in URL instead of query params. In fact this params duplicate role of query
params.
--
Тарас Иващенко (Taras Ivashchenko), OSCP
www.securityaudit.ru
----
"Software is like sex: it's better when it's free." - Linus Torvalds
pgpuM678Dv3Qa.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ W3af-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/w3af-develop
