#1995 Some special cases not handled correctly when resolving URLs

[Joerg Werner]

When resolving the final URL from a base URL and a (relative) path, there are two special cases where HtmlUnit behaves differently compared with real browsers. This happens only if the path starts with "/..".

baseUrl:             "http://www.example.com/some/path"

path:                "/...there-used-to-be-a-time/index.html"
expected target URL: "http://www.example.com/...there-used-to-be-a-time/index.html"
actual target URL:   "http://www.example.com.there-used-to-be-a-time/index.html"

path:                "/..there-used-to-be-a-time/index.html"
expected target URL: "http://www.example.com/..there-used-to-be-a-time/index.html"
actual target URL:   "http://www.example.comthere-used-to-be-a-time/index.html"

I believe I have a fix for that. Will provide a pull request later this evening.

Thanks!

PS: Is this still the right place to report issues or shall we rather use GitHub Issues instead?

[RBRi]

Thanks, PR merged already. The new artifacts are available on the new build machine.

Report future issues here or on github, i will take care of both for the next time.