|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] How many of you are using WebSphere 4 and either the Original HTTP server or Apache as the HTTP front-end? In other words, browser communicates with HTTP server which communicates with WAS 4 via the plug-in? I am having a problem in this scenario with downloading large files. Originally, I had a servlet that was programmatically downloading a large file, like a zip file, but I have also tried it by just placing the zip file within my web site and accessing it by URL. Both fail the same. It works with small files fine, but as soon as I get somewhere between 10-20 MB it fails instantly with a server error (I believe HTTP 500). It works fine if I am accessing the internal WAS HTTP transport, just not when going through the plug-in. Works the same with SSL vs. non-SSL. I also tried it with both Apache and Original HTTP server, making me think the problem is in the plug-in. I am on V4R5 with WAS 4.03 and all of the latest group PTF's. Thanks Mark
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.