On Thu, 09 Sep 2004 08:02:51 -0700, Chris Zoper
<te***********@12move.nl> wrote:
Norton Internet Security blocks some of my ASP.NET pages. The pages are
very 'normal' pages though. There is no 'dangerous' code in it or
something like that. Also, the page is not in a pop-up. Most of my pages
work just fine, but when I navigate to a specific page, it won't open.
We had a similar problem with NIS and our ASP.Net application.
Specifically on our General Manager's XP Pro laptop, which he uses for
product demos with the application installed locally, if NIS is
enabled, then just a _couple_ of the dynamic images (ie *.ASPX pages
outputting dynamic image/png charts) fail to load - red X in browser,
nothing logged anywhere, no exception thrown in our code. That is, two
out of about 30 of these pages (all using the same base class and
output mechanism) are blocked/broken when NIS is enabled.
I don't know if this relates to your experience at all with your
ASP.Net (presumably text/html) pages, but it is only the _largest_ two
of our dynamic charts (heights of about 7000 pixels and 20000 pixels
respectively - displayed in a scrolling DIV) which this issue happens
with, and ONLY when the app is locally hosted (ie the same build of
the code works perfectly when accessed from his laptop over our
intranet or over the net), and not reported by any of our cllients in
any of their "normal" server->client use. Perhaps NIS blocks or has
some overflow when scanning really large locally-sourced (ie
"outgoing") streams, or ones that are generated more slowly, or
something mysterious like that?
As you've described, simply disabling NIS and refreshing the page
makes it work normally, and re-enabling it and refreshing again repros
the problem 100% repeatably (but always only on the same
pages/images).
Aside from the above I can't offer any explanation at all as to why
just two pages out of our entire app would be affected by NIS (and
also why it seems only a problem with local/loopback use of the
ASP.Net app with NIS, not when the same laptop accesses the same
application on a server). We ended up simply taking the advice of
Symantec and Microsoft that NIS and IIS just don't get on (IIS is for
servers, NIS is for workstations), and our GM is now using NAV
together with the XPSP2 firewall and no problems at all.
ted.h.
--
Ted Harper (Sydney, Australia)