DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39105>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39105 ------- Additional Comments From [EMAIL PROTECTED] 2006-03-26 15:55 ------- (In reply to comment #5) > Created an attachment (id=17984) --> (http://issues.apache.org/bugzilla/attachment.cgi?id=17984&action=view) [edit] > test case in utf8 > > Writing file in unicode solves problem but one cant mix unicode and other Ok. At least my thoughs have been correct. > 1-byte charsets in file. And koi8-r and cp1251 are main charsets for russian > internet while uniode in uncommon. > There is nothing in > http://httpd.apache.org/docs/2.0/env.html > http://httpd.apache.org/docs/2.0/howto/ssi.html > http://httpd.apache.org/docs/2.0/mod/mod_include.html > about utf8. Actually it would have to be in the documentation of mod_cgi. But I admit that it is not mentioned there. > Even if we close eyes on charsets and so then there is still strange behaviour > of apache: > - why httpd can include static html files while there are non latin1 symbols > in > non utf8 in variables? > - why httpd can successfully assign and print these variables? > - why httpd talks about "mod_include: Options +Includes (or IncludesNoExec) > wasn't set, INCLUDES filter removed, referer: doesnt_works.html" in log file? > does it removes filter when it find attempt to include cgi while there are non > latin1 characters in non utf8 in enviroment variables? > - why this happens in windows only? :) (at least in linux it does works with > variables in any charset) This is because you try to execute an cgi script. The variables set via mod_include get exported to the environment of the cgi script to be run by mod_cgi. On Windows the values of these environment variables are expected to be UTF-8 encoded and they will be reencoded to UCS2 before executing the script. As this fails several error messages get written to the log file. I admit that they are confusing. The only relevant one is the first: (22)Invalid argument: utf8 to ucs2 conversion failed on this string: xxx=\xe6\xee\xef\xe0 The others get created up in the call stack, because apr_conv_utf8_to_ucs2 called by apr_proc_create failed to convert the environment variables. This causes apr_proc_create to fail and so on. > > PS: it is nothing related to bash, same problem is with python also. httpd > doesnt even start cgi - that you can see by creating some file in that cgi so > you will see that no file will be created. Absolutely -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
