Caching and SSL

Hello,

We have recently set up an IIS web site that runs on SSL. Unfortunately,
the performance is now much slower. In looking at the logs, it appears that
I am no longer getting any 304 responses, now they are all 200. Is there a
configuration I can apply that would make IIS start sending 304 responses?
Thanks in advance.

--
Rob Schieber

Re: Caching and SSL

On Dec 3, 7:00 am, "Rob Schieber" wrote:
> Hello,
>
> We have recently set up an IIS web site that runs on SSL. Unfortunately,
> the performance is now much slower. In looking at the logs, it appears that
> I am no longer getting any 304 responses, now they are all 200. Is there a
> configuration I can apply that would make IIS start sending 304 responses?
> Thanks in advance.
>
> --
> Rob Schieber



Can you provide a reason why not sending 304 responses is incorrect in
your situation and is responsible for "slower performance"?

There is no configuration to make IIS start or stop sending 304
responses..

The Handler of the request is responsible for sending 304 response
*if* a qualified request is received. This means that it is critical
for you to indicate:
1. whether the clients sent qualified requests that should result in
304
2. whether the handler of the request sends 304 responses (what is the
resource extension in question, and what is the Application mapping
for that resource extension at the URL namespace in question)

Without these two pieces of information, one cannot determine if 304s
should be sent or not, and since 304 is an optimization and not
requirement, it means that your observations could just be coincidence
and no indication of any misbehavior of IIS.

For example, the IIS Static File Handler has 304 logic for requests
that provide the right If* conditional and ETag which apply regardless
of HTTP or HTTPS. What handler are you talking about, and what request
logic ensures that 304s are supposed to be returned.

For example, I know of servers that serve SSL pages that never return
304s, and that is not a problem because the requests never get to the
IIS Static File Handler and the actual handlers do not have 304 logic.

In other words, unless you can prove that a 304 is supposed to be
returned, the 200s that you see are correct and by-design behavior.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//