From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2001:558:fe21:29:69:252:207:38; helo=resqmta-ch2-06v.sys.comcast.net; envelope-from=eklhad@comcast.net; receiver= 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 47F0577AAF for ; Wed, 7 Mar 2018 04:29:00 -0800 (PST) Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-06v.sys.comcast.net with ESMTP id tYCuem4v7jzb2tYDDeoXYi; Wed, 07 Mar 2018 12:30:27 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1520425827; bh=5C3IKFG3qcVCwkkRYzLNsBmxRdb42gAzOZjwuNd+z9E=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=n9AFgOf30U29AtQH7EPevxwDwanKTbL3KVGL+2I8ryqBTZAxJwTsj2PhUF9oqnGDK AQwfKlhFUfMEFmUN2GZaaxTqxZPFhJC6VCdlbwscr9LjBbYxOawXVGmbRbqi2nx+aK +SPAbkaA25wGFM4PjIlFy/fwYwxgCdGvUa5xDKgDKUo3OyveXpULOUF5A9/OV3sFmT Z1x30F9YqReinBgeT+mAsbpIbNK9DTJWTRVj/StJFqpKIVnSKdZ25/Y8xhOJHqFsBF p3xb9XY7jwdZINt1PXsGcMvgQ5092/2IMsDGn+ingmKzBb9/aZwhyP7KES5Ewj9dCu C98tZDze1QPTA== Received: from unknown ([IPv6:2601:408:c300:8f09:21e:4fff:fec2:a0f1]) by resomta-ch2-17v.sys.comcast.net with SMTP id tYDCeNe292TTTtYDCeBjwb; Wed, 07 Mar 2018 12:30:27 +0000 To: edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20180306233150.GA21533@workshop.attlocal.net> User-Agent: edbrowse/3.7.2 Date: Wed, 07 Mar 2018 07:30:26 -0500 Message-ID: <20180207073026.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=nextpart-eb-351001 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfI/M27nVs0osRWhwUs7nUaxBItKbburQZFuiEOi6WNEOUpSu7pCg7l91QjGVv8ugXEiFT/fMpbSY092xKfhwSHIU7C7lPzH4nxdEsUa04IZz+khvwLtk CeYKnCmH96DkqRoJdKcuTkgZ3SYjp+kisN19HPsqift2mgCPLKLAPDbp Subject: [Edbrowse-dev] A possible login issue on gkg.net X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.25 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 12:29:00 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --nextpart-eb-351001 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable The thing we have to remember, I have to remember, is when the second = page issues a 403 error, there's no point in looking at the second = page, neither its html nor its js nor its css. The error occurred before we got any of that data. It's all about the first page, and the http exchange to fetch the = second page, which looks right to me, according to db4. I did something I haven't done in years, downloaded lynx and ran it. With no screen readers etc, this is the only other browser I can run. I pulled up the home page, put in a fake login and password, went to = the next page, and got the same 403. So lynx doesn't handle it either, and lynx probably does cookies = properly, and certainly sends the post request properly, so that rules = out a couple of things. The next step, which I am not able to do, is to run this in chrome or = firefox and sniff the packets as they go by, and see exactly what http headers it is sending to gkg to get the = second page. If you have a proxy server with monitor perhaps you could use that = instead of a packet sniffer. That might be worthwhile if we were serious about debugging edbrowse in = the ongoing future, so we could compare and contrast internet traffic. Logically, if we send exactly the same http headers as firefox, it will = work. Yes, I tried changing the user agent, that didn't help. By coincidence, tsp ran into a 403 error, and we fixed it by fixing = referer, which is part of the http headers, and was not being sent = properly. I was hoping that was it here, but referer looks right. Karl Dahlke --nextpart-eb-351001--