Ok I get it now. Thanks 

I appreciate the help guys ! I will let you about the final implementation.
It could be helpful for people in the same situation. 

Yann

-----Original Message-----
From: Albert [mailto:pound@alacra.com] 
Sent: February 26, 2007 4:18 PM
To: pound@apsis.ch
Subject: Re: [Pound Mailing List] Maintenance message for back-end



Carbonell, Yann wrote:
  

Thanks this is exactly what I would like to achieve! Actually you are not
confused at all . You pictured it very well . 

The meta-refresh page idea you came with is a great idea  , it would
redirect users after a certain period of time (let's say 10 sec) to the
corresponding back-end. 
However My concern is  whether they will still be able to access the final
application afer being redirected or will end-up in a loop. 

This means that after being displayed the page and redirected, customers
request will be redirected again as you catch all calls at the higher
service level . Am I correct saying that? 
  
    

No, the first service is only catching calls to http://*yourdomain.com/ 
(the regexp is for "/" only).  Your meta-redirect would have to go to 
"http://www.yourdomain.com/index.html" or whatever page is your homepage 
(this way the 2 Services will be skipped).
  

Would it be easier to manage this if we put a front-end portal , that
    

would
  

act as a central web page and redirect users to access back-end
    

application
  

. So I could put the maintenance page on that particular server while
keeping the back-end config.
  
    

Thats really upto you.  However, you must have at least 1 web server 
that returns this "maintenance" page (pound doesn't do this, its only a 
conduit).
  

One more point though, when you say somebody goes to my index.html I think
that they will still be redirected as you have put the redirection on the
upper level .
  
    

This is similar to the question(answer) above.  The regular expression 
is for the root page only.