W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2015

[Bug 28435] [XT30TS] resolve-uri-022

From: <nobody@w3.org>
Date: Thu, 06 Aug 2015 01:11:14 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28435-523-r4mlMTGEjB@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28435

--- Comment #3 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
When writing this test I have tried to be careful to only test for RFC parts
that are mandatory. Such things are, I believe:

* base path with host name, but no trailing slash: slash must be appended,
unless relative path is empty (5.4.3)
* relative path with more ".." segments than in the base path, authority
component remains, host and path must be separated by slash (5.2.4 and 5.4.2)
* base path with dot-segments, after merging these must be removed (5.2.2 and
5.2.4)
* 'overlapping' dotted segments, where removing dotted segments from right to
left or left to right would yield different results. It should be from left to
right (5.2.4)
* relative part starting with "/" and followed by dotted segments: these have
no effect, "/" remains in place (5.2.4)

Most, if not all inspiration for this test comes from the examples in 5.4.1 and
5.4.2. I don't think any part of the RFC allows the resulting path segment to
be a non-root path (i.e. without leading "/"), except for the case of an empty
relative path and an empty path segment in the base path, but that is not
covered by this test.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 6 August 2015 01:11:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:55 UTC