CF 5 supports HTTP 1.1. I dont know if this means full support or just
partial support though.
I hope I am not stepping to far out of line with this paste from 5 beta's
new features docs.
"Until ColdFusion 5.0, ColdFusion used only a line-feed character in
creating response headers returned to clients (browsers). To comply with
HTTP 1.1, ColdFusion now returns both line feed and carriage return
characters in response headers. "
jon
----- Original Message -----
From: "lsellers" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, March 08, 2001 4:51 PM
Subject: RE: CFHTTP & HTTP 1.0
> > A partner we are working with uses name based hosting and needs incoming
> > request to use HTTP 1.1. When I send them a request using CFHTTP
> > they come
> > through using HTTP 1.0.
> >
> > Is there a configuration setting on the IIS machine to change this, or
is
> > this just the way CFHTTP works?
>
> I don't use cf much anymore but it seems like a lot of the complaints
about
> it I've seen over the last few months involve exactly what you're talking
> about it. The host http server is a multi-homed ip and CFHTTP isn't
sending
> the appropriate "host: x" message.
>
> I've verified this through my tcpclient com everytime anyone mentioned a
> public website they were having trouble with through CFHTTP. CFHTTP says
it
> is having connection problems, but tcpclient works fine.
>
> (For the most part this would be a rather easy thing to fix, btw.)
>
> --min
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
