after SSLEngine on can not open https://xxx.com/ errorlog said: [ssl:info] [pid 9223] AH01876: mod_ssl/2.4.2 compiled against Server: Apache/2.4.2, Library: OpenSSL/1.0.1b [mpm_prefork:notice] [pid 9223] AH00163: Apache/2.4.2 (Unix) OpenSSL/1.0.1b configured -- resuming normal operations [mpm_prefork:info] [pid 9223] AH00164: Server built: May 6 2012 09:31:18 [core:info] [pid 9224] [client ] AH00566: request failed: invalid characters in URI I have changed mpm (event and prefork) and close all other modules even openssl-devel and it still have the error . if no ssl it works ok and apache 2.2.22's ssl is normal with the same key and crt on the same server. when I change server/protocol.c 971 ap_log_rerror(APLOG_MARK, APLOG_INFO, 0, r, APLOGNO(00565) 972 "request failed: URI too long (longer than %d)", 973 r->server->limit_req_line); error log said: AH00566: request failed: invalid characters in URI \xf0[\xd4\t\x0c I am sure it is not a Brower problem becuse of changing ie and chrome other info: os:CentOS release 6.2 (Final) cpu:Intel(R) Xeon(R) CPU 5110
sorry I paste wrong code , right is this 975 else if (r->method == NULL) { 976 ap_log_rerror(APLOG_MARK, APLOG_INFO, 0, r, APLOGNO(00566) 977 "request failed: invalid characters in URI %s",r->headers_in); 978 }
The message looks like you are speaking ssl to a non-ssl port. Maybe for some reason, ssl is not enabled on your vhost in the 2.4 version of your config. Please contact a user list to help you debug your config if you don't find the problem yourself. I am marking this as invalid for now. If you still think there is a bug after fixing your config, please reopen. (Insufficient documentation is a bug, too.)