Bug #1653
Issue when passing on XML location through URL
| Status: | New | Start date: | 2016-03-08 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
e.g. in the case of
brechtdeman.com/listeningtest/index.html?url=tests/A.xml
when sent through Facebook, for instance, the forward slash in the url argument becomes the hex code %2F, after which the test can't be opened (and index.html is simply loaded).
Can this be 'caught', i.e. can %2F be parsed back to a forward slash? The alternative is to keep all XML files at top level, which isn't pretty or desirable.
History
#1
Updated by Giulio Moro about 8 years ago
we should always encodeURIComponent() the url, and decodeURIComponent() it before using it.
Note that this way links in the current format will keep working.