Following a bit of research I’ve discovered why I’ve been experiencing so many issues with Urlencoding (as explained in my previous post).
From this page – http://www.permadi.com/tutorial/urlEncoding/ – it would appear that the + sign Collateral Damage buy Barbie Mariposa and Her Butterfly Fairy Friends move becomes %2B
as I thought. However, it also explains that
This is thus a rather complex issue that means urlencoding / un-encoding of a + sign can potentially lead to issues.
I think the source of my issues with this may actually be that continual urlencoding and un-urlencoding means that the stored text is processed twice. The first time, the code will
Impact Pt I movie Immortal Beloved divx
be correctly un-urlencoded, turning all the text into the required format. However, if this text is again un-urlencoded, most of the text will simply be ignored, but the + sign will be processed again – and will appear as a space.
Thus, I suspect the solution to this issue is to look carefully through all the programming to ensure that any stored text is only un-urlencoded once – I suspect the issue is that I’ve asked text to be un-urlencoded more than once, thus causing this rather complicated issue.
1 response so far ↓
1 Andrew Field // Dec 11, 2005 at 1:57 am
This does appear to have solved the issue entirely.
When I ‘double’ urlencoded or ‘double’ un-urlencoded data, this had no effect – apart from the + sign. As this stands for different things depending on whether the data is encoded or not, this created the problem.
All I have done now is vastly simplify when the question data is encoded – this is now only done when data is saved and loaded or when the data is passed onto the finished Flash file.
I’m still working on it, but it is excellent to have discovered the solution to this rather irksome problem
Leave a Comment