On 11/04/2014 09:55 AM, David Singer wrote:
I am pretty puzzled why the base URL <stuff://www.app.com/a/b/> composed with the URL
<banana> results not in
stuff://www.app.com/a/b/banana
but
stuff:///banana
Is this a bug or feature of the spec., or a bug in this implementation?
Please refresh. I've changed the implementation to match the spec.
Spoiler alert: the results returned now don't match either of the values
you mention above.
- Sam Ruby
On Nov 4, 2014, at 14:32 , Anne van Kesteren <ann...@annevk.nl> wrote:
On Tue, Nov 4, 2014 at 3:28 PM, Sam Ruby <ru...@intertwingly.net> wrote:
To help foster discussion, I've made an alternate version of the live URL
parser page, one that enables setting of the base URL:
http://intertwingly.net/projects/pegurl/liveview2.html#foobar://test/x
Of course, if there are any bugs in the proposed reference implementation,
I'm interested in that too.
Per the URL Standard resolving "x" against "test:test" results in
failure, not "test:///x".
--
https://annevankesteren.nl/
David Singer
Manager, Software Standards, Apple Inc.
