You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@sling.apache.org by Robert Munteanu <rm...@adobe.com> on 2012/06/15 15:31:39 UTC

Running Sling behind a web proxy on a different port

Hi,

I'm experiementing with a setup where the Sling launchpad jar is launched standalone on port 8080 and then the connection is proxied to Apache which listens to port 443 and has SSL enabled. 

I've noticed that when authenticating the user is redirected to launchpad's own port (8080) instead of 443. 

My apache configuration is

	ProxyPass /system http://localhost:8080/system
	ProxyPassReverse /system http://localhost:8080/system

	ProxyPass /j_security_check http://localhost:8080/j_security_check
	ProxyPassReverse /j_security_check http://localhost:8080/j_security_check

And my Sling 'test case' is	

$ curl -k -F"j_username=admin" -F"j_password=admin" https://localhost/j_security_check 
(redacted)
> POST /j_security_check HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-unknown-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.0e zlib/1.2.5 c-ares/1.7.5 libidn/1.22 libssh2/1.2.9
> Host: localhost
> Accept: */*
> Content-Length: 254
> Expect: 100-continue
> Content-Type: multipart/form-data; boundary=----------------------------758d454ef5cb
> 
< HTTP/1.1 100 Continue
< HTTP/1.1 302 Found
< Date: Fri, 15 Jun 2012 13:26:48 GMT
< Server: Jetty(6.1.x)
< Location: http://localhost:8080/
< Content-Length: 0
< Set-Cookie: sling.formauth=NmRmNGIyNjNmNTRhOGQ5ZWJiYjIwNGQwYTg0YzhjYjk1ZTEzNDBhMkA0MTMzOTc2ODYwODYyM0BhZG1pbg; Path=/; HttpOnly
< Content-Type: text/plain

Note that the Location header points to port 8080. Is this something which I can configure or should I raise a feature request?

Thanks,

Robert