Yea, I could confirm that my browser transferred the bytes mentioned in my
previous thread.

Yes, I am presently facing problem on the Windows environment.

Could you please help me out with your thoughts, if this is known issue with
apache-1.3 (which seems to be from the link with I had mentioned :-) but I
am not-sure on this.); so that I can proceed further on this.

Thanks a lot in advance.

On Thu, Jan 8, 2009 at 5:34 PM, Eric Covener <[email protected]> wrote:

> On Wed, Jan 7, 2009 at 11:51 PM, sathya sai <[email protected]>
> wrote:
> >
> > The UTF-8 equivalent for あいうえお (URI resource part) is
> > %E3%81%82%E3%81%84%E3%81%86%E3%81%88%E3%81%8A. I use
> > http://hpcgi1.nifty.com/glass/url/url_encode.cgi to verify the same.
>
> That doesn't mean your browser transmitted those bytes.
>
> >
> > And to add-on to this, found
> > http://osdir.com/ml/apache.devel/2002-03/msg00117.html URL which in
> brief
> > mentions the following info,
> >
> >  "Because of the lack of proper support for non-ASCII characters in file
> > names, it is recommended that administrators not attempt to use any
> > non-ASCII characters in file names. Any other configuration is
> > unsupported.
> >
> > Apache 2.0 introduces the UTF-8 convention to access any filenames and
> > resources in a predictable and safe manner. The implementation of this
> > feature is too extensive to consider backporting to Apache 1.3."
> >
> > Does it means that non-ASCII characters in file names are not supported
> in
> > Apache-1.3 ?
> >
>
> That seems to be windows-specific.  Is that your platform?
>
> I'm not familiar enough with 1.3 to know if it tried to perform
> translation on non-windows, but later releases do not.
>
>
> --
>  Eric Covener
> [email protected]
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: [email protected]
>   "   from the digest: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to