Quick Answer:
- HTTP 1.1 Persistent Connection feature (which is used by MS IIS and MS
IE)
- Miscalculated Content-Length header provided by CFAS (thanks to the
combination of CFLOCATION + CFHTMLHEAD)
- MS I.E. trusting the miscalculated values, and clearing its buffer
based on false info.

I am just too lazy to go too deep into the whole thing. I have done it
once on CFTALK. You can search the archives. :P

----------------------------
James Ang
Programmer
MedSeek, Inc.
[EMAIL PROTECTED]



-----Original Message-----
From: cftalk [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, January 16, 2003 8:43 AM
To: CF-Talk
Subject: Re: HTTP header info showing up on CFM pages...(problem with
cflocation)


I think that is what it is...  Thanks for the reply!

Brian
----- Original Message -----
From: "Aaron Johnson" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, January 16, 2003 10:28 AM
Subject: Re: HTTP header info showing up on CFM pages...(problem with
cflocation)


> Hi Brian,
>
> > I fixed it by commenting out the cflocation and adding a JScript to
direct
> > the page.  Has anyone ever had this happen?
> > > I am having a problem with http info showing up on certain pages.
I
am
> > clueless as to why.  Has anyone had any problems with this?  Here's
what's
> > showing up..
> > >
> > > HTTP/1.1 200 OK Server: Microsoft-IIS/5.0 Date: Wed, 15 Jan 2003
21:04:27
> > GMT Connection: close Content-type: text/html cache-control:
no-cache
> > Expires: 0 Pragma: no-cache Page-Completion-Status: Normal
> > Page-Completion-Status: Normal Page-Completion-Status: Normal
> > >
> > > The application.cfm page does have this...
> > >
> > > <cfhtmlhead text="<script language=""javascript"">window.status =
> > ""WelcomHome"";</script>">
> > > <cfif lscriptname is not "somedoc.cfm">
> > >  <cfheader name="cache-control" value="no-cache">
> > >  <cfheader name="Expires" value="0">
> > >  <cfheader name="Pragma" value="no-cache">
> > > </cfif>
>  -- yeah, we've had this happen before... The cause of this is a
> <CFHTMLHEAD> tag with content greater than 1024 characters, positioned
> above a <CFLOCATION> tag.  This is a bad combination... cflocation
> writes to the http headers, and cfhtmlhead writes to the HTML head,
> somehow these two are runnning into each other.
>
> How to fix?  If you've ever got stuff that needs to go in the HTML
head
> that is long text, don't use <CFHTMLHEAD> ... and also try to position
> the logic in your page so that any cflocations are taken care of as
soon
> as possible.
>
> We had this problem about 2 years ago and found a solution on forums,
> which doesn't exist anymore, but you can thank Brett Suwyn
> (mailto:[EMAIL PROTECTED]) who offered the answer in:
>
http://forums.allaire.com/devconf/Thread.cfm?&&Message_ID=411284&_#Messa
ge41
> 1284
>
> AJ
>
> --
> Aaron Johnson
> http://cephas.net/blog/
> [EMAIL PROTECTED]
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Signup for the Fusion Authority news alert and keep up with the latest news in 
ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to