Kobi Gana <kobig...@gmail.com> added the comment:

We are on the same page and we should also consider marked this as defect.

Thanks

On Sun, Feb 17, 2019 at 7:44 PM nr <rep...@bugs.python.org> wrote:

>
> nr <aktio...@googlemail.com> added the comment:
>
> W3C allows both constructs, ampersand and semicolon.
> https://www.w3.org/TR/html401/appendix/notes.html#h-B.2.2
>
> Especially servlet containers and servers running CGI programs often use
> semicolons as a separator.
>
> I would say to parse either ampersands OR semicolons and keep a priority
> to ampersands.
>
> For example the query strings:
>
>
> ?fields=id&query=%22((release%3D{id%3D1004});(sprint%3D{id%3D1040});(team%3D{id%3D1004});(severity%3D{id%3D%27list_node.severity.urgent%27});!phase%3D{id+IN+%27phase.defect.closed%27,%27phase.defect.duplicate%27,%27phase.defect.rejected%27})%22
>
> ?fruits=lemon;lime&family=citrus
>
> should be parsed with & separators only.
>
> The modified example without & character:
> ?fruits=lemon;family=citrus
>
> can be parsed with semicolon as a separator because it contains both '='
> and ';' but no '&' characters.
>
> ----------
> nosy: +nr
>
> _______________________________________
> Python tracker <rep...@bugs.python.org>
> <https://bugs.python.org/issue20116>
> _______________________________________
>

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue20116>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to