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 ...Reverse proxy and absloute linksReverse proxy and absloute links
Previous
 
Next
New Post
6/22/2006 1:12 PM
 

Hello,

In our site we have a single Web front-end and are establishing reverse-proxies to the other machines for the different services (the other machines are not accessible directly for security reasons)

The problem is that if I have a reverse proxy from www.xxx.org/DotNetNuke to http://mymachine:8082/DotNetNuke, the first URL will work and display the home page of my DotNetNuke portal, but then all the links in this page will be like:  http://mymachine:8082/DotNetNuke//Home/tabid/67/ctl/Login/Default.aspx and so they won't work !

So, is there a way of having DotNetNuke using relative links instead of absolute links ! This would allow reverse proxies to work...

Then is there a specific reason why DNN is using absolute links ?

Any help or clarification would be greatly appreciated...

Kind regards.

Dominique

 
New Post
7/18/2006 7:18 AM
 

Hello,

The reverse proxy probably sends the "original external name" (ie www.xxx.org/DotNetNuke)  as "X-Forwarded-Host" - header field that - ideally - DotNetNuke should use as Alias for your site and generate Friendly urls for.  You may do the necessary changes in FriendlyUrlProvider.vb but you may get into troble with templating components (most likely 3rd party components) if they are using image urls like "/images/....".

DotNetNuke is not using absolute links - but uses Aliases to allow several aliases per site. Your problem is that the reversy proxy adds a new alias to your site - and that DotnetNuke at current does not support the "X-Forwarded-Host" header field from the reverse proxy to generate friendly urls.

Kind regards

Jonny Bekkum

 
New Post
7/18/2006 2:20 PM
 

I'm having this problem too. None of my images show up in the proxy and my 3rd party nav bar doesn't work either. How can I get DNN to work through a reverse proxy?

We're using DNN for our intranet and want to make it also available to the outside by employees through our reverse proxy server.

 
New Post
8/7/2006 6:49 AM
 
Hi,

Did you manage to get anywhere with using the site through your reverse proxy server?

Currently have a site which we wish to be able to access using the LAN and externally. We have had to turn "FriendlyUrls" off, which actually then allowed our users the access to our own modules (previously they would see a timeout).

We're finding now that we have turned it off that our users are receiving errors with Page Cannot Be Found and some of our module links are now the same.

Any help or pointers in how you may have achieved this would be greatly appreciated.

Jimski


 
New Post
9/11/2006 4:13 PM
 

I had the same problem reverse proxying a DNN 4.3.1 site with Microsoft ISA server. The solution that worked for me was to disable Friendly URL's in the Host Settings page. I can now access the website without it redirecting to the internal URL after the initial request. No problems reported as of yet.

Hope that helps.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Reverse proxy and absloute linksReverse proxy and absloute links


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