Project

General

Profile

Bug #1016

header Content-Disposition with russian '?' (CP1251, ascii code 255) causes error

Added by Anonymous over 13 years ago. Updated almost 12 years ago.

Status:
Fixed
Priority:
Normal
Category:
mod_proxy_core
Target version:
ASK QUESTIONS IN Forums:

Description

- error

- normal

------part of error.log-------
http_req.c.270: (trace) parsing failed ... (no error-msg)
http_resp.c.247: (trace) parsing failed ...
mod_proxy_core.c.1905: (trace) state: 5 (error)
connections.c.1201: (trace) (error) plugins_call_handle_send_request_content(): r = 5
------end---------------------

-- mixsture


Related issues

Related to Feature #602: Russian letters not alowed?FixedActions
#1

Updated by jwmcglynn over 13 years ago

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

#2

Updated by jwmcglynn about 13 years ago

I think that ASCII 255 should be allowed. It is only a control character for telnet and FTP (which specifically allows some telnet control codes). The HTTP spec doesn't specifically disallow 255, but it also doesn't specifically allow other characters that are currently accepted.

#3

Updated by stbuehler almost 12 years ago

  • Status changed from New to Fixed
  • Resolution set to duplicate
#4

Updated by gstrauss about 4 years ago

  • Related to Feature #602: Russian letters not alowed? added

Also available in: Atom