IE File Download Dialog Hangs with Single-Sign On


when we are attempting to download files (DOC, XLS, JPG, PDF) from our application, the IE file download dialog hangs.

ASP.NET 2.0 / IIS with Integrated Windows Authentication

The events are:
Click button to download file
Postback occurs which retreives file and creates response
Browser receives response header and body of correct size
Browser raises file open/save/cancel dialog.
Regardless of whether choosing open / save...
File Download Progress Dialog appears but data doesn't get populates (e.g. filename / size / progress)
User can cancel otherwise will stay at dialog until session times out.
If the user chose Save then they will never get the option to choose where the file should be saved to.

The files being downloaded are very small (~20-50K)

Having tested the firewall/AV etc we have identified the problem as being with Passlogix Single Sign On (SSO, now Oracle ESSO).

When SSO is turned on, the file download always fails. If shutdown then the file download always succeeds.

The file download succeeds in Firefox but not in IE 6.0SP2. I believe because SSO uses a plugin for IE which isn't present in Firefox.

I've raised this as a new question as the previous question I found on this issue didn't have a solution...

Can anyone help?

Response.ContentType = "Application\octet-stream";
Response.AddHeader("Content-Length", attachmentFile.fileData.Length.ToString());
Response.AddHeader("Content-Disposition","attachment; filename="+attachmentFile.localFilename);

Open in new window

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Try removing bits.  I remember having similar trouble many years ago with IE6 and Content-Disposition.  Also, your ContentType should be "application/octet-stream" (all lower case with a FORWARD slash).

Response.ContentType = "application/octet-stream";

Open in new window

RealtimeEngineeringLtdAuthor Commented:
sorry - that was a typo in the forum. It is as you suggest in the actual code.

Tried setting the mime type to application/msword as well with the same result with the dialog box hanging.

Things also tried:
Response.ClearHeaders() at the start
Response.flush() at the end and before the respone.end
Removing the content length
Actually, your Content-Disposition is missing enclosing "

Response.AddHeader("Content-Disposition","attachment; filename=\""+attachmentFile.localFilename + "\"");

Open in new window

Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Another though, have you inspected the HTTP data between IE and the server using Fiddler?  Compare one session with SSO enabled with one with it disabled.
RealtimeEngineeringLtdAuthor Commented:
I believe the headers are the same. We have limited permissions on the test box we're using but I'll try and install Fiddler and let you know.

Certainly on our test box the headers are identical. I'll check and post the results back

RealtimeEngineeringLtdAuthor Commented:

An example header is as follows:

HTTP/1.1 200 OK
Server: Microsoft-IIS/5.1
Date: Mon, 17 Nov 2008 11:49:56 GMT
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Content-Length: 27648
Content-Disposition: attachment; filename="Control Document 4.doc"
Cache-Control: private
Content-Type: application/octet-stream
RealtimeEngineeringLtdAuthor Commented:
Having checked the headers they are indeed identical.

any more ideas anyone?
RealtimeEngineeringLtdAuthor Commented:
We were using SSO V5.0.4

Following a test upgrade to V6.0 our application worked perfectly. This may have been due to a bugfix or a configuration change between versions.

Our customer's solution to this problem is to uninstall Passlogix SSO v5.0.4 for all users who need access to our application.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
The joy of 3rd party components :o(.

Glad you found a solution albeit not ideal.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.