Feature #602

Russian letters not alowed?

Added by about 13 years ago. Updated almost 3 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Missing in 1.5.x:


Related issues

Related to Bug #1016: header Content-Disposition with russian '?' (CP1251, ascii code 255) causes errorFixed


Associated revisions

Revision b47494d4 (diff)
Added by gstrauss about 3 years ago

[config] opts for http header parsing strictness (fixes #551, fixes #1086, fixes #1184, fixes #2143, #2258, #2281, fixes #946, fixes #1330, fixes #602, #1016)

server.http-parseopt-header-strict = "enable"
server.http-parseopt-host-strict = "enable" (implies host-normalize)
server.http-parseopt-host-normalize = "disable"

defaults retain current behavior, which is strict header parsing
and strict host parsing, with enhancement to normalize IPv4 address
and port number strings.

For lighttpd tests, these need to be enabled (and are by default)
For marginally faster HTTP header parsing for benchmarks, disable these.

To allow
- underscores in hostname
- hypen ('-') at beginning of hostname
- all-numeric TLDs
server.http-parseopt-host-strict = "disable"

"lighttpd doesn't allow underscores in host names"
"hyphen in hostname"
"a numeric tld"
"Numeric tld's"
"Bad Request"
"400 Bad Request when using Numeric TLDs"

To allow a variety of numerical formats to be converted to IP addresses
server.http-parseopt-host-strict = "disable"
server.http-parseopt-host-normalize = "enable"

"URL encoding leads to "400 - Bad Request""
"400 Bad Request when using IP's numeric value ("ip2long()")"

To allow most 8-bit and 7-bit chars in headers
server.http-parseopt-header-strict = "disable" (not recommended)

"Russian letters not alowed?"
"header Content-Disposition with russian '?' (CP1251, ascii code 255) causes error"



Updated by moo about 13 years ago

u should urlencode it. but standard is always lack behind the need of human... relatived bug #551. i'd mark both of the bug enhancement.


Updated by jwmcglynn about 12 years ago

This bug is due to not allowing the ASCII 255 character in the request or response header, and is the same as #1016.


Updated by gstrauss about 3 years ago

  • Related to Bug #1016: header Content-Disposition with russian '?' (CP1251, ascii code 255) causes error added

Updated by gstrauss about 3 years ago

  • Description updated (diff)
  • Status changed from New to Patch Pending
  • Assignee deleted (jan)
  • Priority changed from Urgent to Normal
  • Target version set to 1.4.40

Updated by gstrauss almost 3 years ago

  • Status changed from Patch Pending to Fixed
  • % Done changed from 0 to 100

Also available in: Atom