On 22/05/2015 12:34 p.m., PSA4444 wrote: > That would be true, but we are using a wildcard certificate, and only > rewriting the subdomain, so the certificate is still valid. > > Would squid 3.5 allow us to rewrite the subdomain in a similar way to your > redirect example, without relying on a helper script? The forcedomain= option on the cache_peer directive makes Squid re-write the domain it sends to the peer. If you are truely using two domain names publicly for the same API service you are only causing trouble for yourself and the rest of the Internet. Please don't. If you are working a transition from an old name to a new name then the 301 redirect is the correct way to do it. That ensures the clients are all informed about the new name in a way that does not break anything, AND clients which understand the 301 status will automatically change all their references to the old name to the new one. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
