thank god ... i am not the only want facing this problem !
each time the page is a HTTP POST method, the page is BLANK !
click refresh ... refresh ... and refresh and sometime the page is loaded successfully. i have many users complain to me that when they do online shopping .. until the last page for commitment it return a blank page ... my ass if burning red firing from many users ... damn ...
this is a stupid bug in ISA 2004. there is no problem with ISA 2000. no matter what rule you use. as long as you have a "deny" rule prior to the users allow rule, you will get this problem.
Ok, I've just phoned Microsoft support in the UK on 0870 60 10 100. They tell me that they cannot give me any more information on this problem and they have no release date for SP1 for ISA 2004.
If we want any further information, I have been advised to e-mail details of the problem to firstname.lastname@example.org, who I have been told will investiate this and will come back to me with more information.
Since this thread has been running for nearly 6 months now, and Microsoft have not even documented this problem on the Knowledgebase, I thought it worthwhile to post this information here. Could I encourage anyone experiencing this problem to contact Microsoft and put pressure on them to fix this.
We upgraded from ISA 2000 in the last couple of weeks. I really do not want to waste another weekend downgrading this server, but if ISA 2004 is not capable of providing reliable internet access for our users I am not prepared to keep it on our network.
A workaround that seems to be effective prior to the release of SP1.
Disable all rules containing Content Types. Then on the Allow rules properties page -> Protocols -> Filtering -> Configure <protocol> -> Extensions change the filtering to Block Specified Extension (allow all others) and add in the extensions that are listed in the Content Types plus any others that you may want to add.
BTW we are only using ISA 2004 as a caching server.
Ok, good news guys. Microsoft have a private fix for this and it's available free of charge if you contact Microsoft Support on 0870 60 10 100 (UK number).
Please make sure that you are positive that this is the problem you are experiencing before you call them. As I said, there is no charge for this fix, but you will need to give credit card details to open the case, and Microsoft charge ú199 per issue for any problems not caused by bugs in the software.
The problem will only be experienced on HTTP traffic after an HTTP POST request. Your browser will most likely show a blank page, and the server logs will show that the connection is closed immediately after the request. I had similar symptoms on HTTPS but with a hugely different cause (mentioned above as the site with intermittent problems), so please check this is exactly what is happening to you.
When you call, Microsoft will need Netmon traces from both the internal & external interfaces of your server, plus output from ISAInfo so they can check exactly how your server is configured and verify that you are experiencing this problem. They'll give you details on how to do this when you call.
What actually happens is that after the HTTP Post is sent, the server responds with a '100 continue' header, but with no body. ISA's content filtering then flagged the response as only needing the header and not the body. When the next response (200) arrived, it was only expecting a header so it strips the body from the response and passes just the header to your browser, causing that blank page.
The fix has not been fully regression tested by Microsoft so is not available as a hotfix and is not documented on the knowledgebase yet. It will appear on the knowledgebase when it has been fully tested, but this has been delayed by the work on SP1.
I've been told that the release of ISA SP1 is 'imminent' and will probably happen in the next two to three weeks. Contrary to earlier rumours however, this hotfix will not be included in SP1. Microsoft will re-issue the private fix to anyone who needs it following the launch of SP1, but expect it to be 8-12 weeks after SP1 for this to become a fully tested hotfix.
Pete, my post above should explain the situation in detail.
Microsoft do not charge for known bugs, but they also do not release a KB article until they have a fully tested hotfix. This unfortunately leaves an in between state where you have a known problem, but have to give your credit card details to speak to Microsoft.
I have done this myself several times, and can confirm that while you have to give credit card details, they will not charge you if this is the problem you are experiencing.
The only downside is that you need to be really sure this is the cause of your problem, but there are more than enough details in this discussion for you to check that.
Well, yes you sort of explained it, however you didn't explain how to check the details:-
"Netmon traces from both the internal & external interfaces of your server, plus output from ISAInfo so they can check exactly how your server is configured and verify that you are experiencing this problem"
I suppose the catch is that until you call MS and give them ú199 they won't give you the tests to run or what results they expect, to see if the problem is covered by a free patch.
As your post was about 6 weeks ago I was enquiring if anyone knew whether MS had released a KB about the issue yet, which would save me the gamble with MS support
Yup, but I also said: "They'll give you details on how to do this when you call.".
I'm afraid there is no way around this. You need to check as carefully as you can that you are experiencing this issue and then call Microsoft. They won't charge you at all if you are having this problem, but I'm afraid you have to take that risk.
Microsoft have told me that it'll probably be 8-12 weeks after SP1 before they fully release this patch with it's associated KB article. That's still a couple of months away but everyone who has received the early fix will be notified as soon as it's available. Once I have details on that I'll post an update here with the KB number.
The best suggestion I can give you to test the problem if you're still unsure is to find an ASP site that is giving you problems and test it with content filtering enabled and with content filtering disabled. If you make sure the content filtering you use should not be blocking that site (just block a movie file or something), and you find that you have problems with the filter enabled, you can be fairly sure you're having this problem and should be able to call Microsoft confident that you will not be charged.
I have also a strange problem with ISA 2004 on windows 2003. Have everything working well when I connected directly to ISA 2004. When I go through a gateway which has to scan http traffic, I receive a blank page whether I use windows integrated authentication method. Without authentication, I have no problem. Does anyone have any idea? Medru
I'm having the same problem described in the first post by cschreiner and was wondering if anyone has found a resolution.
I don't have the blank page after post problem, but one where access to sites that don't have audio and video content, e.g. online banking sites which require a login, are blocked. The rule allows HTTP, HTTPS, and FTP with all content except audio and video.