Skip to content

reserved chars escaping is not compatible with what browsers do #18

Description

@kmike

This is weird, but browsers don't usually escape |; Chrome only escapes it in URL path, but not in query; Firefox doesn't escape it at all. See scrapy/w3lib#25 (comment).

Activity

  1. mahmoud commented on Jul 3, 2017

    @mahmoud
    Member

    That's a pretty cool survey of browser behavior you've got in there! It also keenly demonstrates the moving target with trying to emulate browsers. That said I've got some ideas of how to achieve similar behavior, related to #28. In short, make these global behaviors customizable based on a context. It'll probably come after we get a more modern IDNA approach, but it's definitely on the roadmap! :)

  2. glyph commented on Apr 28, 2021

    @glyph
    Collaborator

    (I'd be really interested to see what the WHATWG URL spec says browsers should be doing, here…)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions