Topic: Apache doesn't start if path contains korean characters

[abhay4u]

I'm testing on Windows 7 x64 SP1.

I have downloaded httpd-2.4.9-win32.zip from VC10 Win32 link which includes IPv6 Crypto apr-1.5.0 apr-util-1.5.3 apr-iconv-1.2.1 openssl-1.0.1h zlib-1.2.8 pcre-8.34 libxml2-2.9.1 lua-5.1.5 expat-2.1.0.

I unzipped and installed on my system. Configured SSL. I installed in directory C:\Apache24. Everything worked fine. I accessed site using http and https and it responded well.


Then I uninstalled apache, changed my system locale to Korea. Now my new Apache path was C:\컴퓨터tt\Apache24. I changed path in httpd.conf as well. I installed apache successfully; did syntax check successfully. When I started apache using httpd -k start, the service didn't started. I checked event viewer, there was an error 'The Apache2.4 service terminated with service-specific error Incorrect function.' No logs were dropped in logs folder.

Now I am stuck. What's wrong?

Thanks and regards,
Abhay

[James Blond]

Well that is because of the UTF-8 filename.
Open a cmd.exe

[abhay4u]

You're right. It's is UTF-8 issue. But your solution didn't work. Here is what I get after issuing DOS command

[glsmith]

I'm going to go out on a limb here and figure your .conf file is being saved with ANSI encoding, try saving it with UTF-8 encoding.

I'm assuming Apache is seeing the ANSI encoded file and not decoding it properly. I do not have the Korean language on this computer but I do have UTF-8 characters to play with.

DocumentRoot "/Apache24ah/璉煉撚戀年"
<Directory "/Apache24ah/璉煉撚戀年">

If saved as an ANSI encoded text file I get
AH00526: Syntax error on line 258 of C:/Apache24ah/conf/httpd.conf:
DocumentRoot must be a directory

If saved as a UTF-8 encoded text file it all works just fine.

http://postimg.org/image/wicz6khpv/

[abhay4u]

First of the file is certainly in UTF-8. You can check the file at https://www.dropbox.com/s/vd2caqh3lsftc13/httpd.conf.

When I run syntax check, the result is OK. The service start command simply returns without any error/warning. No logs are generated in logs folder. You can verify in the snapshot https://www.dropbox.com/s/uncdyma5pe8v7bg/img2.png.

Regards,
Abhay

[glsmith]

https://www.dropbox.com/s/uncdyma5pe8v7bg/img2.png

Looks like it's running to me. If there is no logs, check Windows Event viewer for something.

[abhay4u]

No. It's not running. I checked event viewer. It shows same event log as I posted in first post. 'The Apache2.4 service terminated with service-specific error Incorrect function.' No logs were dropped in logs folder.

[James Blond]

Well did you notice revision 1611169 ?

[abhay4u]

I didn't understand much. I only got that it had some UTF-8 related issue. Even if it's solved, the binaries I have downloaded from Apache Lounge doesn't have this fix. So it will be fixed only when new compiled binaries are available.

It'd be more helpful if you provide some details.

Regards,
Abhay

[James Blond]

That fix is currently only in trunk and has not been backported (yet) to 2.4 branch.

[abhay4u]

Hi All,

I would like to thank everyone for their help and support on this topic. I'd wait for the release and see if the issue gets resolved.

I thing that keeps my thought hunting that how come Apache 2.2.3 with OpenSSL 1.0.1g works well with UTF-8 charset. I've tested this version on English, Japanese, Korean, German OS and everything running smooth?

How come UTF-8 support provided in earlier version are not reflected in latest version? I checked with latest 2.4.10 version of Apache and I got the same result as earlier (not working with Korean path).

Regards,
Abhay