Apache 2.2 in ZeroXI and path with accented characters

[Daimonji]

Hi all,

 

When I extract ZeroXI US within a path with accented characters and starts the Apache2 web server, it says the page could not be found.

Of course, no problem with a default path without space characters.

 

It is possible to make it work with a path with accented characters, and if so how ?

I changed the default charset to utf-8 with no luck.

 

Edit: Got the same issue with Apache 2.4.9.

 

Thank you,

Daimonji

[meows]

Server Paths

You can install The Uniform Server Zero in nearly any location, with the exception that the path to folder UniServerZ must not contain spaces. Do not use "C:\Program Files", for example (which has other problems as well, such as restricted permissions and system restore inconsistencies). We recommend installing to the drive root, such as "C:\" or "D:\" for simplicity, but other locations, such as "C:\test1\appserver" work just as well.

Note: The space character restriction is generic and applies to other WAMP stacks as well. Many applications that will be hosted on the server do not tolerate spaces in paths. The system restore issue applies mainly to individual component installs.

 

so no it will not work, I imagine English only? a-z 1-0

Hi all,

 

When I extract ZeroXI US within a path with accented characters and starts the Apache2 web server, it says the page could not be found.

Of course, no problem with a default path without space characters.

 

It is possible to make it work with a path with accented characters, and if so how ?

I changed the default charset to utf-8 with no luck.

 

Edit: Got the same issue with Apache 2.4.9.

 

Thank you,

Daimonji

[Daimonji]

Thank you for your answer but... it doesn't help much. The no space character in path is known and makes cense. However, a path with any accented character won't but is quite common except for English and Americain people, but you won't have any warning.

 

Replace 'C:\test1\appserver' by 'C:\test1\appserver_testé' and see for yourself. This is probably a default charset or encoding issue, but I was unable to solve this.

 

Daimonji