B
Brent Martin
Been struggling with the following for awhile. If anyone could lead
me in the right direction, I sure would appreciate it...
We have an IIS web server that returns a "404" error whenever a file
with an ".axd" extension is requested (trace.axd, webresource.axd,
etc...). We originally had the .NET 2.0 Beta 2 Framework installed on
it (and had this problem back then), and recently upgraded to the
final 2.0 release--hoping that it would fix the problem (but it
didn't). We have three other web servers with similar setups, and they
work fine.
In IIS Manager, I've verified that the ".axd" application extension's
option "Check that file exists" is unchecked. We're not doing anything
with HTTP compression. We haven't made any wildcard application
mappings. Any ideas on where else I should look to get the server to
return ".axd" files?
Thanks...
me in the right direction, I sure would appreciate it...
We have an IIS web server that returns a "404" error whenever a file
with an ".axd" extension is requested (trace.axd, webresource.axd,
etc...). We originally had the .NET 2.0 Beta 2 Framework installed on
it (and had this problem back then), and recently upgraded to the
final 2.0 release--hoping that it would fix the problem (but it
didn't). We have three other web servers with similar setups, and they
work fine.
In IIS Manager, I've verified that the ".axd" application extension's
option "Check that file exists" is unchecked. We're not doing anything
with HTTP compression. We haven't made any wildcard application
mappings. Any ideas on where else I should look to get the server to
return ".axd" files?
Thanks...