Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

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 DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...URL Rewrites worked in QA, but now not in productionURL Rewrites worked in QA, but now not in production
Previous
 
Next
New Post
6/24/2010 10:28 PM
 
Somewhat of an urgent question - since all of this checked out in QA, but now is not working in Production.

Details:
QA and Production sites are both on the same web server.  Different IIS folders (or whatever their called) and separate app pools

QA URL: http://qa.mysite.org/Magazine-eNewsletter/Magazine-Archive.aspx
WWW URL: http://www.mysite.org/Magazine-eNewsletter/Magazine-Archive.aspx

 SHOULD rewrite to... /Resources/Magazine-eNewsletter/Magazine-Archive.aspx

Friendly URLs are enabled - and my rewrite rule is...
MATCH: .*.org/Magazine-eNewsletter(.*)
 REPLACE WITH: http://www.mysite.org/Resources/Magazine-eNewsletter$1

Now... I know I could go through the database and change all the links - but we rearranged the heirarchy of the pages - so there are MANY, MANY more rules like this.  And, I know that people have bookmarks out there, so I would really like to put them where they belong - rather than showing an error page.

Also - I know I can create dummy pages on the server for each "broken" page requested - but there are HUNDREDs.  Most of these are newsletter archives - going back to 2006.

Any and all help would be greatly appreciated!!
 
New Post
6/25/2010 8:04 AM
 
If you have different domain names, it will be different sites in IIS.

The rewrite rule can't work on "www.mysite.org" site because the request dont go to this dnn site.
They go to the "qa.mysite.org" site (because the configuration of IIS).

If you want this rewrite rule work, you have to put the domain "qa.mysite.org" on the same IIS site then "www.mysite.org".
And maybe add it also to the site alias of the  "www.mysite.org" dnn site.

If you do this, it work also without the rewrite rule.

But the best way was, maybe to put relative link in the urls. So it had works with the 2 domain names.

I hope it was a answer to your question....
 
New Post
6/25/2010 8:25 AM
 
Maybe I didn't explain it well enough. I don't see why putting the QA and WWW on the same IIS site would make any difference? I'm not concerned that it has to work on both domains - with relative urls. in QA my rewrite rule was.. MATCH: .*.org/Magazine-eNewsletter(.*) REPLACE WITH: http://qa.mysite.org/Resources/Magazine-eNewsletter$1 in WWW my rewrite rule is... MATCH: .*.org/Magazine-eNewsletter(.*) REPLACE WITH: http://www.mysite.org/Resources/Magazine-eNewsletter$1 So, why does the QA rewrite rule work - and the WWW one does not?
 
New Post
6/28/2010 11:02 AM
 
When your browser ask to IIS for the url "http://qa.mysite.org/Resources/Magazine-eNewslette...." IIS reroute the request based on the header qa.mysite.org.

So thr request is rerouted to the "qa.mysite.org" IIS site. And the rewrite rule in the dnn site of "www....." have no chance to be evaluated.

(sure a make some assumtion about your IIS config)
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...URL Rewrites worked in QA, but now not in productionURL Rewrites worked in QA, but now not in production


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out