Hello Kavya,
My application collects URIs while crawling a web site. I checked that every major web browser (IE11, Chrome, Firefox) can navigate the web site and accept the bad URIs I reported previously. However regarding your question 1, I noticed that IE11 rejects such URIs (see screenshot), whereas both Chrome and Firefox send
![IE11 error message]()
Regarding your 2nd question, could you bring an example of URI where
My application collects URIs while crawling a web site. I checked that every major web browser (IE11, Chrome, Firefox) can navigate the web site and accept the bad URIs I reported previously. However regarding your question 1, I noticed that IE11 rejects such URIs (see screenshot), whereas both Chrome and Firefox send
GET /encodedstr1%C5%9Fend/encodedstr2%xyend HTTP/1.1 so their URI parser does not fail (but I did not delve into the code to see how they are parsed). Still, if IE11 rejects that URI, they are probably rarely found in real life.
Regarding your 2nd question, could you bring an example of URI where
/ would be ambiguous? I cannot see where I would consider encoding that character. Maybe ?, # or & would be more challenging.