From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38])
	by hurricane.the-brannons.com (Postfix) with ESMTPS id 7F74C77AE4
	for <edbrowse-dev@lists.the-brannons.com>; Sun, 30 Jun 2019 21:43:31 -0700 (PDT)
Received: from resomta-ch2-03v.sys.comcast.net ([69.252.207.99])
	by resqmta-ch2-06v.sys.comcast.net with ESMTP
	id ho8UhyMLA3MGrhoA6hH8kg; Mon, 01 Jul 2019 04:43:30 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
	s=20190202a; t=1561956210;
	bh=/kDT56umrwdphb2O8+KccVc+73i0GHUTFQESZcWVrTc=;
	h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID:
	 Mime-Version:Content-Type;
	b=VH4pa7hh2fHO5fll8Iqc9ACyvKXCKt2pGjCo9Lw8d6c47REnuZpo1Lns3gtEbhy+W
	 OXE0IrR5lcqhT7Kt1sAHoMrEcmJEqVIurIX0zSXv0EL7cpbUCnPL0vqs2T0GkrnV8c
	 C1vaMR+JKYILLRLXCSjbDGx2ds1O+XxmyvpHQ3jS0T9YVFeSF7kbEpmBVPhEYsh80L
	 mqn80/bssEtbDt5g2ldfE6FaUgb08ATc1kgCbMmMyezVR3dghajm2yJYSiLqVfT4jl
	 XoJU1xRsFkNeMzYCQVPxFj1GBc6mC43ROGOeoCotEOzoomxtjd1G96gutoTGtyUL9g
	 0pJzYfHVzbUZA==
Received: from unknown ([IPv6:2601:408:c303:3f49:21e:4fff:fec2:a0f1])
	by resomta-ch2-03v.sys.comcast.net with ESMTPSA
	id hoA5htT3bOoCZhoA6hh6Hl; Mon, 01 Jul 2019 04:43:30 +0000
X-Xfinity-VMeta: sc=0;st=legit
To:edbrowse-dev@lists.the-brannons.com
From: Karl Dahlke <eklhad@comcast.net>
Reply-to: Karl Dahlke <eklhad@comcast.net>
References: <alpine.DEB.2.21.1906302035090.6731@carhart.net>
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)
Subject: [edbrowse-dev] resolveURL question
Date: Mon, 01 Jul 2019 00:43:43 -0400
Message-ID: <20190601004343.eklhad@comcast.net>
X-BeenThere: edbrowse-dev@edbrowse.org
List-Id: Edbrowse Development List <edbrowse-dev.edbrowse.org>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

resolveURL seems like such a simple routine, but it has been a nightmare for about 15 years now.
That's why I have specific debug prints for it, at level 5, probably should be at level 4.
We need to see what it is doing and when it screwes up, like here.

The section you refer to is not relevant.
rel is the variable of the relative piece, and that code is for
rel = #foo
where I'm just changing the hash.
But here we have a new path, and the base has a hash, but the hash contains a slash, which I've never seen before.
parseURL handles it properly, so let's step through and see what goes wrong.
Line 885 is telling us where the problem is.
Fortunately the fix is literally a single character.

Karl Dahlke