FYI,

MS IE 6.0 will have trouble on some (many?) PC's when returning a https download response. Modifying the cache and pragma headers in appendToResponse of the "download" page does not work since I guess WO tacks on the expiration, cache and pragma headers after the page appenToResponse. I implemented the Microsoft workaround by over-riding dispatchRequest in Application and implementing the header manipulation for content-type = application/octet-stream responses.

I just wanted to share this with anyone who has been encountering this issue. More details are show in the MS kb articles referenced in the code snippet. If the more wiser among the community has a better practice implementation of this workaround (such as putting this in application appendToResponse instead of dispatchRequest), then let me know.

Regards, Kieran

    public WOResponse dispatchRequest(WORequest request) {
        WOResponse aResponse = super.dispatchRequest( request );

        // A workaround to fix https downloads bug in IE
        // See Microsoft knowledge base articles 812935, 323308
        // http://support.microsoft.com/kb/812935/en-us
        // http://support.microsoft.com/kb/323308/en-us
// Remove the cache-control: no-store and cache-control: no-cache headers

        String contentType = aResponse.headerForKey( "content-type" );

if ( contentType != null && contentType.equals( "application/octet-stream" ) ) {

            // Modify the headers
            aResponse.removeHeadersForKey( "cache-control" );
            aResponse.removeHeadersForKey( "pragma" );

            // Set age to a long time allowing caching
            aResponse.setHeader("max-age=604800","cache-control");

        }

        return aResponse;
    }

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to