Port Mapping

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

What operating system were you running when the bug appeared?
What database platform is your site using?
What version of mojoPortal are you running?
What version of .NET do you use?
What steps are necessary to reproduce the issue? Compare expected results vs actual results.

This thread is closed to new posts. You must sign in to post in the forums.

5/12/2010 12:12:43 AM

Riana

Total Posts 2

View Posts

Port Mapping

My client is hosting their website on their own internal server which is also a proxy server

This is their current setup:

- The server hosts their web site under IIS with port 8080
- External requests to www.website.com (port 80) are translated to internal requests to the server (port 8080)
- Port number 8080 was chosen as this server is also a proxy server and port 80 is already in use – this cannot be changed
- Identified the below option in the web.config file:

Setting this value to true displays the website correctly within their Network while externally it shows with no styles

Setting this value to false has the opposite effect: internally it shows with no styles while externally it shows up fine.

Is there some way to work around this in the web.config? The client is adament that a second rule created on the router is not an option.

You must sign in to post in the forums. This thread is closed to new posts.