[Pound Mailing List] Redirect from apache backend with different subdomain fails

Hi folks,

I have a strange issue and I hope someone can help me out!

I had a website run under https://www.domain.tld/myfuture/. Now it 
should be available under https://myfuture.domain.tld
Therefore I inserted a .htaccess rule inside the apache folder:
Redirect 301 /myfuture/ https://myfuture.domain.tld

And it works perfect. Inside varnish.log I can see the correct response 
header:
-   BerespProtocol HTTP/1.1
-   BerespStatus   301
-   BerespReason   Moved Permanently
-   BerespHeader   Date: Tue, 13 Sep 2016 07:36:31 GMT
-   BerespHeader   Server: Apache/2.4.10 (Debian)
-   BerespHeader   Location: https://myfuture.domain.tld
-   BerespHeader   Cache-Control: max-age=1209600
-   BerespHeader   Expires: Tue, 27 Sep 2016 07:36:31 GMT
-   BerespHeader   Content-Length: 318
-   BerespHeader   Content-Type: text/html; charset=iso-8859-1

But pound did not deliver the correct response. With wget I receive 
https://www.domain.tld instead of https://myfuture.domain.tld which I 
expected.

wget -S https://www.domain.tld/myfuture

Connecting to www.domain.tld|81.169.218.xxx|:443... connected.
HTTP request sent, awaiting response...
   HTTP/1.1 301 Moved Permanently
   Date: Tue, 13 Sep 2016 07:36:31 GMT
   Server: Apache/2.4.10 (Debian)
   Location: https://www.domain.tld
   Cache-Control: max-age=1209600
   Expires: Tue, 27 Sep 2016 07:36:31 GMT
   Content-Type: text/html; charset=iso-8859-1
   X-Varnish: 491606
   Age: 0
   Via: 1.1 varnish-v4
   Transfer-Encoding: chunked
   Connection: keep-alive

The configuration is as followed:

pound ---> varnish ---> apache

I suppose that pound changes the subdomain myfuture to www because www 
is the requested subdomain. Is that true and how could I change this 
behavior?

Cheers Neal











--
To unsubscribe send an email with subject unsubscribe to [email protected]
Please contact [email protected] for questions.