edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] another encoding question
Date: Fri, 25 May 2018 16:50:11 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1805251636070.8696@carhart.net> (raw)

Around February I was trying to add urlencode() calls to the XHR code and 
try to say "this needs a call because it's not encoded yet."

At that time, Karl sez:

> I take issue with your encoded decoded test, because I've been down
> that path before.

> There is simply no way to tell if a url is encoded.

So acknowledging this, I am wondering if there is something we can do 
about the following xhr call from radio caroline, and any others that 
would be on this pattern.  It doesn't work with a space and it does work 
with a %20.

xhr http://radiocaroline.co.uk/website_prefs.json?v=2018-05-25 23:31:19.890+00:00
GET /website_prefs.json?v=2018-05-25 23:31:19.890+00:00 HTTP/1.1
Host: radiocaroline.co.uk

HTTP/1.1 400 Bad Request


When I just go to startwinow, replace spaces with %20 just before 
fetchHTTP and recompile, the load of website_prefs succeeds and this 
triggers a whole bunch of new things like the long list 
of available 'g' links to different sections.  (Whether the links work is 
another matter but when website_prefs succeeds, at least they render in 
the first place.)

GET /website_prefs.json?v=2018-05-25%2023:33:04.754+00:00 HTTP/1.1
Host: radiocaroline.co.uk

HTTP/1.1 200 OK

                 reply	other threads:[~2018-05-25 23:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.03.1805251636070.8696@carhart.net \
    --to=kevin@carhart.net \
    --cc=edbrowse-dev@lists.the-brannons.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).