Re: [PHP] None US ASCII characters not allowed in headers?
On Sun, June 10, 2007 12:48 am, Robert Cummings wrote: > On Sun, 2007-06-10 at 13:36 +0800, Crayon Shin Chan wrote: >> On Sunday 10 June 2007 04:05, Robert Cummings wrote: >> >> > Funny how the solution often presents itself after you make your >> > problem public *lol* :) Wonder if it falls under Murphy's Law. >> >> There should be a dummy list that people post to, if they don't work >> out >> the answer themselves 10 minutes after posting to the dummy list >> they can >> then post to the real list. > > *lol* The first time I read the above I thought you were suggesting a > list to which idiots could post :) No, I think we have that already... :-) :-) :-) Hey, *I* am here, right? -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] None US ASCII characters not allowed in headers?
On Sun, 2007-06-10 at 13:36 +0800, Crayon Shin Chan wrote: > On Sunday 10 June 2007 04:05, Robert Cummings wrote: > > > Funny how the solution often presents itself after you make your > > problem public *lol* :) Wonder if it falls under Murphy's Law. > > There should be a dummy list that people post to, if they don't work out > the answer themselves 10 minutes after posting to the dummy list they can > then post to the real list. *lol* The first time I read the above I thought you were suggesting a list to which idiots could post :) Cheers, Rob. -- .. | InterJinn Application Framework - http://www.interjinn.com | :: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] None US ASCII characters not allowed in headers?
On Sunday 10 June 2007 04:05, Robert Cummings wrote: > Funny how the solution often presents itself after you make your > problem public *lol* :) Wonder if it falls under Murphy's Law. There should be a dummy list that people post to, if they don't work out the answer themselves 10 minutes after posting to the dummy list they can then post to the real list. -- Crayon -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] None US ASCII characters not allowed in headers?
On Sat, June 9, 2007 3:05 pm, Robert Cummings wrote: > On Sat, 2007-06-09 at 21:59 +0200, Frank Arensmeier wrote: >> Sorry, my misstake. It turned out that the filename (stored in >> MySQL) >> was UTF8 encoded. Setting the content header filename value >> "manually" to something including umlaut characters was no problem. > > Funny how the solution often presents itself after you make your > problem > public *lol* :) Wonder if it falls under Murphy's Law. 31st Corollary. -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] None US ASCII characters not allowed in headers?
On Sat, June 9, 2007 2:51 pm, Frank Arensmeier wrote: > I have been struggling with a little problem for quite some time now, > without finding a good solution. > > On one of my pages, users are able to download files that contain > none US ASCII characters in their filenames (e.g. character ö,ä,å). > And I would like to set the original filename in the content header. > But according to RFC2183 on "... The Content-Dispostion Header > Field", characters that are not part of US ASCII are not allowed in > content headers. Is there any chance to get around this limitation? > On the other hand, uploading files that contain "special characters" > in their filenames is no problem. Why is that so? My "solution" so > far is that I simply replace those characters (ä with a, ö with o and > so on). If those characters are valid in URLs, or can be URL-encoded to be valid, then this rant may let you achieve your goal, bypassing the Content-disposition issue(s): http://richardlynch.blogspot.com -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] None US ASCII characters not allowed in headers?
On 6/9/07, Robert Cummings <[EMAIL PROTECTED]> wrote: On Sat, 2007-06-09 at 22:20 +0200, Frank Arensmeier wrote: > 9 jun 2007 kl. 22.05 skrev Robert Cummings: > > > On Sat, 2007-06-09 at 21:59 +0200, Frank Arensmeier wrote: > >> Sorry, my misstake. It turned out that the filename (stored in MySQL) > >> was UTF8 encoded. Setting the content header filename value > >> "manually" to something including umlaut characters was no problem. > > > > Funny how the solution often presents itself after you make your > > problem > > public *lol* :) Wonder if it falls under Murphy's Law. > > ... I think you made a good point there ... Happens to me all the time. Cheers, Rob. -- Yup, happens to me too.. Tijnema -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] None US ASCII characters not allowed in headers?
On Sat, 2007-06-09 at 22:20 +0200, Frank Arensmeier wrote: > 9 jun 2007 kl. 22.05 skrev Robert Cummings: > > > On Sat, 2007-06-09 at 21:59 +0200, Frank Arensmeier wrote: > >> Sorry, my misstake. It turned out that the filename (stored in MySQL) > >> was UTF8 encoded. Setting the content header filename value > >> "manually" to something including umlaut characters was no problem. > > > > Funny how the solution often presents itself after you make your > > problem > > public *lol* :) Wonder if it falls under Murphy's Law. > > ... I think you made a good point there ... Happens to me all the time. Cheers, Rob. -- .. | InterJinn Application Framework - http://www.interjinn.com | :: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] None US ASCII characters not allowed in headers?
9 jun 2007 kl. 22.05 skrev Robert Cummings: On Sat, 2007-06-09 at 21:59 +0200, Frank Arensmeier wrote: Sorry, my misstake. It turned out that the filename (stored in MySQL) was UTF8 encoded. Setting the content header filename value "manually" to something including umlaut characters was no problem. Funny how the solution often presents itself after you make your problem public *lol* :) Wonder if it falls under Murphy's Law. ... I think you made a good point there ... //frank Cheers, Rob. -- .. | InterJinn Application Framework - http://www.interjinn.com | :: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] None US ASCII characters not allowed in headers?
On Sat, 2007-06-09 at 21:59 +0200, Frank Arensmeier wrote: > Sorry, my misstake. It turned out that the filename (stored in MySQL) > was UTF8 encoded. Setting the content header filename value > "manually" to something including umlaut characters was no problem. Funny how the solution often presents itself after you make your problem public *lol* :) Wonder if it falls under Murphy's Law. Cheers, Rob. -- .. | InterJinn Application Framework - http://www.interjinn.com | :: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] None US ASCII characters not allowed in headers?
Sorry, my misstake. It turned out that the filename (stored in MySQL) was UTF8 encoded. Setting the content header filename value "manually" to something including umlaut characters was no problem. Lazy me... Nice weekend. //frank 9 jun 2007 kl. 21.51 skrev Frank Arensmeier: Hi. I have been struggling with a little problem for quite some time now, without finding a good solution. On one of my pages, users are able to download files that contain none US ASCII characters in their filenames (e.g. character ö,ä,å). And I would like to set the original filename in the content header. But according to RFC2183 on "... The Content-Dispostion Header Field", characters that are not part of US ASCII are not allowed in content headers. Is there any chance to get around this limitation? On the other hand, uploading files that contain "special characters" in their filenames is no problem. Why is that so? My "solution" so far is that I simply replace those characters (ä with a, ö with o and so on). Any ideas? //frank -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] None US ASCII characters not allowed in headers?
Hi. I have been struggling with a little problem for quite some time now, without finding a good solution. On one of my pages, users are able to download files that contain none US ASCII characters in their filenames (e.g. character ö,ä,å). And I would like to set the original filename in the content header. But according to RFC2183 on "... The Content-Dispostion Header Field", characters that are not part of US ASCII are not allowed in content headers. Is there any chance to get around this limitation? On the other hand, uploading files that contain "special characters" in their filenames is no problem. Why is that so? My "solution" so far is that I simply replace those characters (ä with a, ö with o and so on). Any ideas? //frank -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
