On Tue, Feb 21, 2006 at 04:58:01PM -0600, Richard Lynch wrote: > You'd have to check if URL-encoding supports whatever sort of > characters/data is your input. > > I would *THINK* that URL-encoding standard would support binary data > of any kind, and be the correct way to do this, in THEORY. > > In PRACTICE, it may be that the implementation of URL-encode would not > correctly handle binary data. > > So you might be stuck with base64-encoding as a work-around... > > I'm pretty sure that base64-encoding output consists only of: > 0123456789ABCDEF and newline and maybe the = sign as a continuation > character? I may be confusing base64 with something else though... Yeah you are correct. There usually 2 =='s at the end of base64 encoded as well, so urlencode should be used without a doubt on top of base64. Of course, the best solution would be to do a file upload of the binary data instead. If file upload is used, there wont be any of this need to mess around with all this base64 encoding/decoding and url encoding stuff, it is already taken care of. Curt. -- cat .signature: No such file or directory -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
