I'm hoping somebody here might be able to help us with a problem we're
experiencing.

We have enabled some Ajax elements on our .Net homepage, and for some
reason, whenever anyone using Hughes Network as an ISP hits our page,
they are generating 404's on any of the .js files Ajax uses.

For instance:
MicrosoftAjax.debug.js
MicrosoftAjaxTimer.debug.js
MicrosoftAjaxWebForms.debug.js

There are about 9-10 different files that can generate these errors.

In the various ScriptResource.axd files that are generated, we see
code like this at the top:

// (c) Copyright Microsoft Corporation.
// This source is subject to the Microsoft Permissive License.
// See http://www.microsoft.com/resources/s...elicenses.mspx.
// All other rights reserved.


/// <reference name="MicrosoftAjax.debug.js" />
/// <reference name="MicrosoftAjaxTimer.debug.js" />
/// <reference name="MicrosoftAjaxWebForms.debug.js" />

and then the actual JavaScript follows below that.

So first, we want to know if the Hughes Network user is actually
experiencing an issue, since I don't believe ANYTHING should be trying
to reference these .js files as they do not reside on our server. And
if it was supposed to be calling this file, it would show up as a 404
for more than Hughes Network surfers.

If it's not necessary, and is not generating an error for the user, is
there any way of making sure their browsers (or is it their proxy
server?) try not to retrieve this file, generating a 404 on our end.

If you believe you can help, but need additional information, let me
know what you need. I could give you several IP addresses the errors
were generated from if necessary, or give you the URL to our homepage
if there's anything on there you need to look at, but I don't think
going to our page is needed as it's not an issue for 98-99% of our
users.

Thanks,

Chris T.

On Jan 12, 9:07*am, Tifer <chris.ti...@gmail.com> wrote:
> I'm hoping somebody here might be able to help us with a problem we're
> experiencing.
>
> We have enabled some Ajax elements on our .Net homepage, and for some
> reason, whenever anyone using Hughes Network as an ISP hits our page,
> they are generating 404's on any of the .js files Ajax uses.
>
> For instance:
> *MicrosoftAjax.debug.js
> *MicrosoftAjaxTimer.debug.js
> *MicrosoftAjaxWebForms.debug.js
>
> There are about 9-10 different files that can generate these errors.
>
> In the various ScriptResource.axd files that are generated, we see
> code like this at the top:
>
> // (c) Copyright Microsoft Corporation.
> // This source is subject to the Microsoft Permissive License.
> // Seehttp://www.microsoft.com/resources/sharedsource/licensingbasics/share....
> // All other rights reserved.
>
> /// <reference name="MicrosoftAjax.debug.js" />
> /// <reference name="MicrosoftAjaxTimer.debug.js" />
> /// <reference name="MicrosoftAjaxWebForms.debug.js" />
>
> and then the actual JavaScript follows below that.
>
> So first, we want to know if the Hughes Network user is actually
> experiencing an issue, since I don't believe ANYTHING should be trying
> to reference these .js files as they do not reside on our server. And
> if it was supposed to be calling this file, it would show up as a 404
> for more than Hughes Network surfers.
>
> If it's not necessary, and is not generating an error for the user, is
> there any way of making sure their browsers (or is it their proxy
> server?) try not to retrieve this file, generating a 404 on our end.
>
> If you believe you can help, but need additional information, let me
> know what you need. I could give you several IP addresses the errors
> were generated from if necessary, or give you the URL to our homepage
> if there's anything on there you need to look at, but I don't think
> going to our page is needed as it's not an issue for 98-99% of our
> users.
>
> Thanks,
>
> Chris T.

Does anyone have a suggestion on a better group to post this to in
hopes of finding an answer?

Or perhaps some better resource than a NG?

have you tried:

http://forums.asp.net/default.aspx?GroupID=34


"Tifer" <(E-Mail Removed)> wrote in message
news:5c9954f6-e86e-4223-aad2-(E-Mail Removed)...
On Jan 12, 9:07 am, Tifer <chris.ti...@gmail.com> wrote:
> I'm hoping somebody here might be able to help us with a problem we're
> experiencing.
>
> We have enabled some Ajax elements on our .Net homepage, and for some
> reason, whenever anyone using Hughes Network as an ISP hits our page,
> they are generating 404's on any of the .js files Ajax uses.
>
> For instance:
> MicrosoftAjax.debug.js
> MicrosoftAjaxTimer.debug.js
> MicrosoftAjaxWebForms.debug.js
>
> There are about 9-10 different files that can generate these errors.
>
> In the various ScriptResource.axd files that are generated, we see
> code like this at the top:
>
> // (c) Copyright Microsoft Corporation.
> // This source is subject to the Microsoft Permissive License.
> //
> Seehttp://www.microsoft.com/resources/sharedsource/licensingbasics/share....
> // All other rights reserved.
>
> /// <reference name="MicrosoftAjax.debug.js" />
> /// <reference name="MicrosoftAjaxTimer.debug.js" />
> /// <reference name="MicrosoftAjaxWebForms.debug.js" />
>
> and then the actual JavaScript follows below that.
>
> So first, we want to know if the Hughes Network user is actually
> experiencing an issue, since I don't believe ANYTHING should be trying
> to reference these .js files as they do not reside on our server. And
> if it was supposed to be calling this file, it would show up as a 404
> for more than Hughes Network surfers.
>
> If it's not necessary, and is not generating an error for the user, is
> there any way of making sure their browsers (or is it their proxy
> server?) try not to retrieve this file, generating a 404 on our end.
>
> If you believe you can help, but need additional information, let me
> know what you need. I could give you several IP addresses the errors
> were generated from if necessary, or give you the URL to our homepage
> if there's anything on there you need to look at, but I don't think
> going to our page is needed as it's not an issue for 98-99% of our
> users.
>
> Thanks,
>
> Chris T.

Does anyone have a suggestion on a better group to post this to in
hopes of finding an answer?

Or perhaps some better resource than a NG?