Greetings to all forum members. Today I have a question about 302 permanent redirections on css/js resource requests.

A few days ago I moved one of our DNN installs from an old production server to the new Azure server. Back up and restore all went smoothly but when I brought up the site I noticed that the login page didn't display correctly. At first, didn't give it much thought as everything else looked fine. A few days later the issue persists.

What I have noticed is that a bunch of css/js files that are being requested return 302 redirects which link to none existent URLs resulting in 404 errors.

For example: /Portals/_default/default.css?cdv=270
Returns: 302 Found - Object moved to /Account/Login?ReturnUrl=%2fPortals%2f_default%2fdefault.css%3fcdv%3d270&cdv=270
But of course, /Account/Login?ReturnUrl=%2fPortals%2f_default%2fdefault.css%3fcdv%3d270&cdv=270 is not a real URL which results in a 404.

This has me puzzled as to how/where this 302 redirects coming from. I know I can setup 302 redirects on a page. But I do not remember setting up specific resource redirects. Can't think of a need to do so.

The second stranges this is that this install is not the first one to move but is the first one to display such odd behaviour. I checked database tables, config files, skin files and nothing odd jumped out at me.

I did a bit of digging around but found not exact issue reported. Kind of similar issue some had to do with GoDaddy hosting or using Active Directory provider. But I am not using either of those.

Not really sure where to go with this one. If anyone has any constructive suggestion please let me know.

Help is appreciated.