W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2009

[whatwg] URL encoding for XHR and Workers.

From: Dmitry Titov <dimich@chromium.org>
Date: Tue, 10 Mar 2009 11:54:25 -0700
Message-ID: <28040fc60903101154h6b3f3825t994806970285376a@mail.gmail.com>
Filed a bug on URL encoding,
https://bugzilla.mozilla.org/show_bug.cgi?id=482388

On Mon, Mar 9, 2009 at 5:02 PM, Jonas Sicking <jonas at sicking.cc> wrote:

> On Fri, Mar 6, 2009 at 4:51 PM, Dmitry Titov <dimich at chromium.org> wrote:
> > Hi,
> > I have a couple of questions about Web Workers and text encoding of URLs.
> > Usually, 'server' and 'path' portions of URLs are always sent in UTRF-8,
> the
> > 'query' portion may be sent encoded if it contains non-ascii characters.
> I'm
> > looking at what should be an encoding used for this.
> > Lets say we have the Page that creates a Worker which uses includeScripts
> to
> > load the NestedScript.
> > Lets say the Page has some text encoding (from http header, meta tag or
> > otherwise). For example, in latest FF nightly (Minefield) the following
> > behaviors can be observed:
> > - XmlHttpRequest created on the Page would send its URL to server encoded
> > using UTF8, irrespective to the encoding of the Page. However, a
> > XmlHttpRequest created in the Worker would send the URL encoded using
> Page's
> > encoding. It seems that either XHR on the Page should also use Page's
> > encoding, or XHR in the Worker should use UTF-8. Bug?
>
> Sounds like it. Would be great if you could file a bug. That is why we
> have beta releases :)
>
> > - When a script of the Worker is decoded, the encoding of the Page is
> used,
> > unless Worker's script comes with http header overriding the ecncoding.
> That
> > sounds right. However, if the Worker in turn creates a nested Worker,
> uses
> > an XHR or importScripts(url), the URL encoding defaults back to the
> Page's,
> > even if there was overriding http header. It might be ok but seems a bit
> > illogical - the nested worker or imported scripts are 'sub resources',
> their
> > relative url is resolved against the Worker's base url, so it feels that
> > their default encoding should be inherited from Worker. Is it a bug?
>
> I suspect so yes.
>
> / Jonas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090310/57716574/attachment.htm>
Received on Tuesday, 10 March 2009 11:54:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:47:49 GMT