httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 9223] - Execution of CGI with multibyte query string fail.
Date Mon, 17 Jun 2002 17:32:11 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9223>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9223

Execution of CGI with multibyte query string fail.





------- Additional Comments From wrowe@apache.org  2002-06-17 17:32 -------

  To elaborate [briefly]... as a stop-gap, we aught to consider treating the 
  values 0x80-0xff as 0x0080 - 0x00ff if they aren't directly convertable 
  to utf-8, and providing some switch for this or other alternate behaviors.

  The alternate behaviors I'm describing are apps that use the local code page
  rather than Unicode for their startup.  This aught to be as simple as using
  the Win32 MultiByteToWideChar API, but there is a deeper problem.

  CGIs authored in a command.com style use the OEM code page, while CGIs 
  authored to Windows binaries use the ANSI code page.  Bleck.  But we know
  the binary even before we begin translating the environment, so we should
  be able to figure out what code page is supported, and whether there is a
  Unicode or Ansi entry point function in the binary we are invoking.

  There is also a mod_encoding module that has been discussed on the webdav
  module development list, I'll research how that could help lick this issue.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message