Redirect a frontend URL to another backend webserver?

For a start please try using Location instead of Directory Directory is used for identifying directory paths on the filesystem not paths relative to the document root Location '/dev/app'> AuthType Basic AuthName "Test Omgeving" AuthUserFile /var/trac/htpasswd Require valid-user.

For a start please try using Location instead of Directory. Directory is used for identifying directory paths on the filesystem not paths relative to the document root. AuthType Basic AuthName "Test Omgeving" AuthUserFile /var/trac/htpasswd Require valid-user.

Thanks, this solves indeed the authentication issue, the 404 remains though. But great that one already thing works :) – Jasper May 4 at 13:20 +1 for catching the – clmarquart May 4 at 13:23 1 To figure out where the 404 is coming from (the backend proxy server or the apache instance) can you tail the access/error logs on the backend server to see what's being requested there and whether it's got any useful error messages? – James C May 4 at 13:38 I'm going to take a look into the logging of the back-end framework, the thing is, it's all supposed to be "full-stack", so the backend webserver is hidden for the developer.

But there is support for logging, so I'll start there. Thanks! – Jasper May 4 at 14:27.

Try the following. It should prompt for the username/password and then pass the request to 127.0.0.1:9000" rel="nofollow">127.0.0.1:9000. In my case, Apache gives a "Service Temporarily Unvavailable", which you should get as well if you turn off the application running on port 9000 ServerName my.website.Com AuthType Basic AuthName "Test Omgeving" AuthUserFile passwd/.

Htpasswd Require valid-user ProxyPass 127.0.0.1:9000" rel="nofollow">127.0.0.1:9000 ProxyPassReverse 127.0.0.1:9000" rel="nofollow">127.0.0.1:9000 If you still get a 404, can you confirm that it's not the backend server sending it?

Great answer, thanks. I still get the 404, but when I'm executing lynx localhost:9000, that works fine. So the server is indeed sending every response.So the problem lies between apache requesting pages from play... – Jasper May 4 at 13:53 The strangest thing... When I execute this lynx 127.0.0.1:9000, it keeps waiting for a request... I'm trying to look in some play configuration files... I'll keep you posted – Jasper May 4 at 14:04 But lynx 127.0.0.1:9000 works... – Jasper May 4 at 14:06 But when I try to edit the ProxyPass directive by removing the "", it generates an error indicating that the paths have to be absolute... – Jasper May 4 at 14:09 1 That is correct, the http:// is needed.

The problem you are having with accessing 127.0.0.1:9000 versus 127.0.0.1:9000 is not something in Apache. Unless you have Apache set to Listen 9000, which by the sounds of it, you do not, that is more likely to be a problem with the backend application/server. – clmarquart May 4 at 14:12.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.