Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.
Yay... Take Me to the Community!
Welcome to the Community Exchange, where community members ask and answer questions about DNN. To get started, just start typing your question below and either select one of the suggested questions or ask a new question of your own.
Return to previous page
Greetings to all forum members. Today I have a question about 302 permanent redirections on css/js resource requests.
Backup and existing install (files and db). Restored to new IIS site, app pool, folder and DB on the same server (copy of the site basically). Back up and restore all went smoothly but when I brought up the site I noticed that the login page didn't display correctly.
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=270Returns: 302 Found - Object moved to /Account/Login?ReturnUrl=%2fPortals%2f_default%2fdefault.css%3fcdv%3d270&cdv=270But 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. Why is DNN appending /Account/Login
The second strange thing is that is that this install is not the first time I have restored it (we use it for all base installs). I checked database tables, config files, skin files and nothing odd jumped out at me.
Not really sure where to go with this one. If anyone has any constructive suggestion please let me know.
Help is appreciated.