Curious Issue

One of clients has a locked down page they get to through the Login snippet.

The page is in a Resource Group called X.
The user group is also called X and includes Resource Group Access and Context access set to Load, List, and View all for the web context as well as the context the site is in.

In Internet Explorer they can login and go to the protected page successfully.

However, when they click a link (to a word document that sits at the root of the site) they get a Windows Security pop up that says:

Windows Security - title bar
Connecting to thewebsite.com

Then it asks for a username and password and to remember the credentials.

Obviously this should not appear.

Any ideas would be appreciated. We have turned up our security settings on our own Explorer and this never happens.

That kind of sounds like a protection applied at the server rather than a MODX issue.

It might also be related to www versus non-www access.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

We looked, there is no protection applied to the server but agree that's what it looks like. If a user input www. when first going to the site all the links remain with the www. If they enter without it, all the links remain without it so there isn't a shift in the source urls.

We have remapped the download to a Static Resource and are awaiting the client's feedback if that changed anything.

I would try uncommenting the code in .htaccess that forces either www or non-www. If a user crosses over during a session (or MODX thinks they have), you'd lose the session info and thus login status.

Even if it doesn't help, it's a good idea from an SEO standpoint.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

We did this and haven't had any other reports of the issue and will indeed do this for every site we develop. Thanks.