Re: Multiple Web Sites on one A5 WAS
After 24 hours of effort, it is my analysis that without specific modifications by Alpha, Alpha Five WAS cannot be run behind Apache or any other web server front-end.
For those interested, the hurdle at the moment is displayed in Gregory's last post with an image attachment, where it says "myweb/myweb/". The fact is you can tell Apache what the DocumentRoot is, but I can find no way for Apache to tell ALPHA what the DocumentRoot is. So in each case where Alpha places a Form Submit button or other action involving a CallBack, the path or Form Action is based on what Alpha understands the DocumentRoot to be, what is set in the AlphaWAS configuration.
Running from Apache, login totally fails under IE8 for some reason, but works from Firefox and Chrome. But the problem in the paragraph above has nothing to do with security, it has to do with what Alpha thinks is the path.
I say this is "not possible" because even if the above is solved, there are going to be other issues. A couple of the guys on this conversation have overcome some issues, only to find other problems.
BTW, I can see how everything might work if each web folder was run on a separate instance of AlphaWAS, allowing me to assign a different DocumentRoot to each website directly in Alpha's configuration. I may try this. This does not defeat the purpose, because the purpose was never to 'bypass' Alpha's licensing regarding Instances, it was to provide better security to the web application, and open up avenues for load balancing, etc.
The fact is that Alpha does not support running their web server under Apache and they would have to officially support this, and make modifications, to allow it to happen, and that's not likely to happen.
If you want to try this, the most recent Apache script below will work up to the point I described (I don't mean my specific URL's will work, I have already removed those from my DNS).
I'd be glad to work with anyone that goes through the steps to test this and knows what they are doing, and has a good idea.
After 24 hours of effort, it is my analysis that without specific modifications by Alpha, Alpha Five WAS cannot be run behind Apache or any other web server front-end.
For those interested, the hurdle at the moment is displayed in Gregory's last post with an image attachment, where it says "myweb/myweb/". The fact is you can tell Apache what the DocumentRoot is, but I can find no way for Apache to tell ALPHA what the DocumentRoot is. So in each case where Alpha places a Form Submit button or other action involving a CallBack, the path or Form Action is based on what Alpha understands the DocumentRoot to be, what is set in the AlphaWAS configuration.
Running from Apache, login totally fails under IE8 for some reason, but works from Firefox and Chrome. But the problem in the paragraph above has nothing to do with security, it has to do with what Alpha thinks is the path.
I say this is "not possible" because even if the above is solved, there are going to be other issues. A couple of the guys on this conversation have overcome some issues, only to find other problems.
BTW, I can see how everything might work if each web folder was run on a separate instance of AlphaWAS, allowing me to assign a different DocumentRoot to each website directly in Alpha's configuration. I may try this. This does not defeat the purpose, because the purpose was never to 'bypass' Alpha's licensing regarding Instances, it was to provide better security to the web application, and open up avenues for load balancing, etc.
The fact is that Alpha does not support running their web server under Apache and they would have to officially support this, and make modifications, to allow it to happen, and that's not likely to happen.
If you want to try this, the most recent Apache script below will work up to the point I described (I don't mean my specific URL's will work, I have already removed those from my DNS).
I'd be glad to work with anyone that goes through the steps to test this and knows what they are doing, and has a good idea.
Comment