You could try rewriting utf-8 representation of umlaut [or other
common char people type into the URL directly] into your local
codepage representation.
this works. is not my preferred solution for this but it works for now. i
will fix my ftp-server to store filenames utf8
Thanks,
Hajo
--
On Tue, Mar 20, 2012 at 9:35 AM, Hajo Locke wrote:
>
>>> Use links that are URL-encoded with the proper bytes so clients don't
>>> have to choose the codepage to request in.
>
>
> hmm, but when typing url directly in browser in most cases utf8 is used by
> browser.
> how to solve this?
You could
Use links that are URL-encoded with the proper bytes so clients don't
have to choose the codepage to request in.
hmm, but when typing url directly in browser in most cases utf8 is used by
browser.
how to solve this?
Thanks,
Hajo
--
On Tue, Mar 20, 2012 at 8:35 AM, Hajo Locke wrote:
> Hello List,
>
> i have some files with german umlauts ö ä ü in filename and want to request
> them by http.
> filename is coded in latin1, in console/ftp etc. all works well and looks
> good.
> when requesting file ü.txt i see this error in log:
Hello List,
i have some files with german umlauts ö ä ü in filename and want to request
them by http.
filename is coded in latin1, in console/ftp etc. all works well and looks
good.
when requesting file ü.txt i see this error in log:
File does not exist: \xc3\xbc.txt
It just works if i recode
