| Author |
|
eriqn Newbie

Joined: 14 August 2010
Online Status: Offline Posts: 2
|
| Posted: 14 August 2010 at 5:12am | IP Logged
|
|
|
I've been advised that I might be able to use Helicon Ape
for a project I'm working on. Here's the scenario:
I have a 2008 R2 server running IIS 7 that is hosting an
application delivered via SSL. Let's say that the
external URL for this app is https://www.domain.com/app1.
I have another app that has its own built-in web engine
that is not delivered via IIS. To get both services
running on the 2008 box, I've set up two IPs on the box
and tied IIS to one IP and the other app to the second
IP. This way I can access the second app as
https://app.domain.com/app2.
This is all well and good in my shop where I have
multiple static IPs and can do all the fun with public
DNS and internal routing for the two IPs, but what I'd
really like is to find a way to have both apps delivered
through the same public URL, as in
https://www.domain.com/app1 for the first and
https://www.domain.com/app2 for the second.
Would Helicon Ape be able to handle this given that both
apps must be delivered via HTTPS/SSL? And if so, how
might I approach that config?
TiA!
-Eriq
|
| Back to Top |
|
| |
Vyacheslav Admin Group

Joined: 02 July 2008 Location: Ukraine
Online Status: Offline Posts: 1535
|
| Posted: 16 August 2010 at 7:40am | IP Logged
|
|
|
Hello,
Yes, Helicon Ape can do this. You will need proxy. Here is an example (assuming Ape was set on domain.com):
Code:
RewriteEngine on
RewriteProxy ^app2(.*)$ https://app.domain.com/app2$1 [NC,L] |
|
|
So when you request https://www.domain.com/app2 the content is actually delivered from https://app.domain.com/app2
Please let me know if that’s what you wanted.
__________________ Slavik Shynkarenko,
Helicon Tech.
|
| Back to Top |
|
| |
eriqn Newbie

Joined: 14 August 2010
Online Status: Offline Posts: 2
|
| Posted: 06 September 2010 at 4:19pm | IP Logged
|
|
|
Sorry for the delay in getting back with you, Slava. It's taken this long for
me to get to a point where I could test this.
In short, it's not working. Well, what you've suggested anyway. I have IIS 7
set up on a 2008 R2 server. I have HeliconApe installed. The basic web
services work fine until I start to try to modify the .htaccess.
I entered the content exactly as you described above (substituting the
app2 fo the actual path to the URL in question), restart the page in IIS, and
all of the content in the main site becomes inaccessible. As soon as I
comment out the contents of the .htaccess file and restart the site, the
expected content starts working again.
To be clear, there is a page at https://app.domain.com, another at
https://app.domain.com/app1 (along with a few other URLs off the root
domain) that need to stay working. It's only the
https://app.domain.com/app2 URL that I need to redirect.
Any other suggestions?
-Eriq
|
| Back to Top |
|
| |
Vyacheslav Admin Group

Joined: 02 July 2008 Location: Ukraine
Online Status: Offline Posts: 1535
|
| Posted: 06 September 2010 at 6:15pm | IP Logged
|
|
|
Hello,
Please send to support@helicontech.com the follows:
1. Your actual code
2. The address that you request
3. The actual address from which the content is delivered
Thanks.
__________________ Slavik Shynkarenko,
Helicon Tech.
|
| Back to Top |
|
| |
|
|
If you wish to post a reply to this topic you must first login
If you are not already registered you must first register
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You can vote in polls in this forum
|