from what I understand if the backend site was not rewriting all request to the domain www.vanguardia.com.mx the proxy would be changing the host with out the need of the rewrite rules..
What you are suggestion is to have my front with a directory in the case the backend does not match the required host (that needs a rewrite function)?
if I set a different context than / I will get 404 from the target since its interpreted as a directorie :-/
No need to create directory. The rewrite rules should be able to handle.
Quote:
Originally Posted by gdewey
from what I understand if the backend site was not rewriting all request to the domain www.vanguardia.com.mx the proxy would be changing the host with out the need of the rewrite rules..
It is the proxy handles the host header rewrite. Backend server does not do anything differently.
To be more efficient, you may pm the server temp access for us to check. Once a solution is worked out, it can be published on forum for other's benefit.
mh I have it on a virtual machine on my lap because I am evaluating the functionality, let me set up a server in the office so I can publish it an give you access
I set up new server in my LAN to test the reverse proxy/cache and it does what it suppose. there must be something with the first try that was not right.
the server / proxy / cache solution is very precise and fast seem to be as fast as varnish or aicache servers. I will have to make a load test this week.
by the way, is there a way to expire cache on a non time based basis? that is using an http request or something that I can control with certain criteria?
will be streaming some xml files to load some grids and graphics but they will come in unexpected times. I need to refresh the cache when they come in.
a http api would be very nice to have so we can just curl/http some url and expire the cache
seem to be as fast as varnish or aicache servers. I will have to make a load test this week.
Linear Mode
