René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"receiveHTTP does not preprocess the incoming URI before it is parsed","articleBody":"Because of the strict parsing of URIs by Network.URI.parseURIReference, parseRequestHead fails on this \"almost valid\" URI:\n\n```\nghci\u003e parseRequestHead [\"GET http://fonts.googleapis.com/css?family=Roboto:300|Open+Sans:700|Open+Sans:300\u0026lang=en HTTP/1.1\"]\nghci\u003e Left (ErrorParse \"parseRequestHead Request command line parse failure: GET http://fonts.googleapis.com/css?family=Roboto:300|Open+Sans:700|Open+Sans:300\u0026lang=en HTTP/1.1\")\n```\n\nReplacing the pipe characters with %7C allows the URI to parse.\n\nreceiveHTTP,  or maybe parseRequestHead, should probably try to escape the characters that are considered invalid for URIs, before sending the string through parseURIReference.\n\nIn that regard, `escapeURIString isAllowedInURI` from Network.URI may be handy.\n\n(Something about \"be conservative in what you send, be liberal in what you accept\" prompted me to raise this issue.)\n","author":{"url":"https://github.com/zkf","@type":"Person","name":"zkf"},"datePublished":"2014-09-04T13:19:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/76/HTTP/issues/76"}