#2334 closed defect (fixed)
XhrIframeProxy: Safari mangles urls when hex escaping sequence is segmented
| Reported by: | James Burke | Owned by: | James Burke |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | IO | Version: | 0.4.1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Safari will add extra hex escaping if the URL fragment identifiers are split between a hex escaped character. For example, if %3C is split so that one fragment ends with the % and the other fragment starts with 3C, Safari will add an extra "25" after the % character on the first fragment.
The solution is to make sure that the urls are split so that hex escaped sequences are preserved. In the above example, end the fragment right before the %3C.
Test case:
- Change one of the iframeproxy tests to pass a large amount of XML data. You have to play with the XML size to get it just right so that the fragments split between a hex escape.
Change History (4)
comment:1 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 Changed 14 years ago by
(In [7055]) References #2314 and References #2334. Issues with XhrIframeProxy?? in MSIE 7 and Safari. (merge from trunk)
Note: See
TracTickets for help on using
tickets.
(In [7034]) Fixes #2314 and Fixes #2334. Issues with XhrIframeProxy? in MSIE 7 and Safari.