Hi Steve, After further investigation the problem seems to occur when going from version 0.9.8i to 0.9.8j.
Kind Regards, Sam. -----Original Message----- From: Gardner, Sam Sent: 25 May 2011 11:44 To: 'r...@openssl.org' Cc: openssl-dev@openssl.org Subject: RE: [openssl.org #2524] openssl 1.0.0d bug report/ query Hi Steve, I'm using curl 7.21.6 to make the request. When I build it with openssl 0.9.8i uppercase hostnames work fine. However, when I build curl with openssl 1.0.0d I get a 400 (bad request) with uppercase hostnames, but only with https requests. Http requests are fine. Any ideas? Kind Regards, Sam. -----Original Message----- From: Stephen Henson via RT [mailto:r...@openssl.org] Sent: 24 May 2011 18:29 To: Gardner, Sam Cc: openssl-dev@openssl.org Subject: [openssl.org #2524] openssl 1.0.0d bug report/ query > [sam.gard...@echostar.com - Mon May 23 12:29:05 2011]: > > Hi, > > I have recently upgraded from openssl 0.9.8i to 1.0.0d, and noticed > that if the host name is in upper case that I get a 400 (bad > request) when doing a https request. This was working in version > 0.9.8i. My OS is Linux. Is there a fix for this? > I'm not sure this has anything to do with OpenSSL. Which application are you specifying the host name? Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
