Header problem in CMS 5?

Dan Ydén

Vote:

Hi everyone,

I have compared the header results from two web servers, one running EPiSerrver and the other one running EPiServer CMS 5 and it seems like CMS 5 sends "connection: close" in 304 (not modified) headers which EPi 4 doesn't.

Is this correct and is there a way to turn it off in CMS 5?

Best regards,
Dan

#24108

Sep 24, 2008 12:57

Per Bjurström

Vote:

Its not correct and not something we do on purpose. I have tried to reproduce it but I can't.

Which version of EPiServer CMS?
Which operating system and service pack ?
Which .NET version and service pack ?
Which type of requests, is it everthing or just pages or just images in some folders or.. ?
Any third-party plugins installed ?

#24122

Sep 24, 2008 19:47

Dan Ydén

Vote:

EPiServer 5.1.422.122
Windows 2003 32-bit standard edition, SP2
.NET 2.0 SP1, .NET 3.0 SP1 and .NET 2.0 Ajax extensions 1.0
StarCommunity 3 & StarMail

I get this problem on all static content (like CSS, JS, Pictures etc) when the server returns a 304 not modified header.

HTTP/1.x 304 Not Modified
Connection: close
Date: Thu, 25 Sep 2008 05:53:23 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private

I have this problem on several EPi 5 sites.

#24133

Edited, Sep 25, 2008 8:08

Per Bjurström

Vote:

Ok - I can reproduce it and have created a bug (#14668), thanks for reporting this. It looks like ASP.NET or IIS is closing the connection when Content-Lenght is not set.

This is only a problem on Windows Server 2003/IIS 6, I cannot reproduce it on Windows Server 2008/IIS 7.

#24151

Sep 25, 2008 14:52

Dan Ydén

Vote:

Ok, thanks for verifying this.
Do you think there will be a fix in the near future?

#24154

Sep 25, 2008 15:42

Per Bjurström

Vote:

It will be fixed in the next version which should be SP1 for EPiServer CMS 5 R2. I really can't say when but I am guessing within a few months from now.

#24178

Sep 26, 2008 9:25

Dan Ydén

Vote:

Will this be solved within a near future?

#26733

Dec 17, 2008 14:37

Per Bjurström

Vote:

This bug has been fixed and tested.

The SP1 update is going into a testing and stabilization phase later this week. Usually we need a month for this phase to complete.

#26736

Dec 17, 2008 16:35