On Sat, Jun 27, 2015 at 6:03 PM, James Moe <ji...@sohnen-moe.com> wrote:
> $ curl -v "http://sma-v3.sma.com/catalog/?testing=123"; > * Trying 192.168.69.246... > * Connected to sma-v3.sma.com (192.168.69.246) port 80 (#0) > > GET /catalog/?testing=123 HTTP/1.1 Host: sma-v3.sma.com User-Agent: > > curl/7.42.1 Accept: */* > > > < HTTP/1.1 302 Found > < Date: Sun, 28 Jun 2015 00:59:03 GMT > < Server: Apache/2.4.10 (Linux/SUSE) > < Location: https://sma-v3.sma.com/clickcart/?testing=123 > < Content-Length: 313 > < Content-Type: text/html; charset=iso-8859-1 > < > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>302 Found</title> > </head><body> > <h1>Found</h1> > <p>The document has moved <a > href="https://sma-v3.sma.com/clickcart/?testing=123";>here</a>.</p> > <hr> > <address>Apache/2.4.10 (Linux/SUSE) Server at sma-v3.sma.com Port > 80</address> > </body></html> > * Connection #0 to host sma-v3.sma.com left intact Okay, the Apache documentation says that the Redirect directive has precedence over Alias and ScriptAlias directives. It doesn't say anything about RewriteRule directives. But I'm willing to bet that's the problem since it would be strange to use both RewriteRule and Redirect in the same context. What happens if you remove the Redirect directive? -- Kurtis Rader Caretaker of the exceptional canines Junior and Hank
