[Webkit-unassigned] [Bug 136938] XMLHttpRequest should have a responseURL attribute (added in recent XHR specification drafts)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=136938





--- Comment #27 from Shivakumar J M <shiva.jm at samsung.com>  2014-10-14 22:18:41 PST ---
(In reply to comment #26)
> > As per build bot test results, it looks fragments in URL are not filtered.
> 
> Should they be? How did you determine that?


Dear Alexey,

     Below are my observations:

     After testing with fragment URL: "resources/supported-xml-content-types.cgi?type=foo#bar/baz+xml" using xmlhttprequest-responseURL.html test file in my local Linux build setup, the returned response URL was "http://127.0.0.1:8000/xmlhttprequest/resources/supported-xml-content-types.cgi?type=foo", so i felt the fragment in URL is getting filtered.

     But when these tests ran in build bot, i got the returned response URL was "http://127.0.0.1:8000/xmlhttprequest/resources/supported-xml-content-types.cgi?type=foo#bar/baz+xml", so i felt fragment in URL are not filtered.


     As per https://url.spec.whatwg.org/#concept-url-serializer ( "If the exclude fragment flag is unset and url's fragment is non-null, append "#" concatenated with url's fragment to output"), if exclude fragment flag is set then only the fragment in URL will be filtered. But i saw URL.cpp, where fragments are addressed, but could not get based on fragment flag how the filtering is happening.

     pls share your inputs, if my understanding is not correct.

Thanks

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.