>Just to close the discussion here:
>Chris sent me the real domain name and I had a look:
>The issue is actually that the ProxyPassReverse is not correct.
>Requests for the main page come back with a 302 pointing to /share/ and all
>assets used also have /share/ at the beginning of their path.
Just to close the discussion here:
Chris sent me the real domain name and I had a look:
The issue is actually that the ProxyPassReverse is not correct.
Requests for the main page come back with a 302 pointing to /share/ and all
assets used also have /share/ at the beginning of their path.
I will h
Sent from my iPhone
> On Oct 31, 2013, at 10:06 PM, "Yehuda Katz" wrote:
>
> When you say "And this gives me a 403 access denied.", you need to also
> include the exact URL that you entered in the browser (minus the hostname if
> you want).
Sorry, https://share.example.com
>
> If you have t
When you say "And this gives me a 403 access denied.", you need to also
include the exact URL that you entered in the browser (minus the hostname
if you want).
If you have the rewrite rule:
*RewriteRule ^/(.*) https://192.168.123.3:8443/$1 [P]*
and you navigate to https://share.example.com/, you s
>Are you accessing this URL from a web browser or a dedicated program?
>The implication is that your client might be requesting (or the web
>application redirecting to) https://share.example.com/share/ which you are
>rewriting to already include the >/share/, therefore, the doubled share.
Acce
Are you accessing this URL from a web browser or a dedicated program?
The implication is that your client might be requesting (or the web
application redirecting to) https://share.example.com/share/ which you are
rewriting to already include the /share/, therefore, the doubled share.
- Y
On Thu,
>What about when you go to https://share.example.com/share/ ?
If i remember right, this gave the same error.
As i try different things and think about this, i am going to need multiple
clients to access this web app securely like so https://share.anydomain.tld and
will need apache to send tho
What about when you go to https://share.example.com/share/?
- Y
On Thu, Oct 31, 2013 at 12:59 PM, Chris Arnold
wrote:
> *>*Is HTTPD giving that error or Tomcat?
>
> HTTPD
>
> >What does the log say is the reason?
>
> Directory index forbidden by directive: /srv/www/htdocs
>
> Is HTTPD giving that error or Tomcat?
HTTPD
>What does the log say is the reason?
Directory index forbidden by directive: /srv/www/htdocs
Is HTTPD giving that error or Tomcat?
What does the log say is the reason?
- Y
On Thu, Oct 31, 2013 at 12:15 PM, Chris Arnold
wrote:
> >>What URL are you using to access this vhost?
>
>> >If you want to access https://example.com/share/ and have that hit the
>> proxy, you would need to make t
>>What URL are you using to access this vhost?
>If you want to access https://example.com/share/ and have that hit the proxy,
>you would need to make the proxy config
ProxyPass /share/ https://192.168.123.3:8443/share/
https://share.example.com which will end up being
https://share.ex
On Thu, Oct 31, 2013 at 11:42 AM, Chris Arnold
wrote:
> The trailing slash is important.
>>
> ProxyPass / https://192.168.123.3:8443/share
>
> >This is telling Apache to strip off the slash when it does the proxy.
> This is probably not what you want to do.
>
> I removed the trailing slash
>
I me
On Thu, Oct 31, 2013 at 3:06 PM, Chris Arnold
wrote:
>>First of all, is "/folder/", "/path/" or "/share/"? You seem to have
>>used them all so far.. please be careful when anonymizing your config
>>that you aren't removing information that is necessary to determine
>>what is wrong
>
> This rea
The trailing slash is important.
ProxyPass / https://192.168.123.3:8443/share
>This is telling Apache to strip off the slash when it does the proxy. This is
>probably not what you want to do.
I removed the trailing slash
>What URL are you using to access this vhost?
>If you want t
On Thu, Oct 31, 2013 at 11:08 AM, Chris Arnold
wrote:
> >Did you have a trailing slash in the ProxyPass?
> >I would expect that it would have tried to get /share*/*share/.
>
> Yes, i had a trailing slash and it did in fact tried to get /share/share.
> When i remove the trailing slash it gives me /
>Did you have a trailing slash in the ProxyPass?
>I would expect that it would have tried to get /share / share/.
Yes, i had a trailing slash and it did in fact tried to get /share/share. When
i remove the trailing slash it gives me /shareshare
>First of all, is "/folder/", "/path/" or "/share/"? You seem to have
>used them all so far.. please be careful when anonymizing your config
>that you aren't removing information that is necessary to determine
>what is wrong
This really shouldn't matter what it is /folder /path/ or /share as l
On Thu, Oct 31, 2013 at 2:20 PM, Chris Arnold
wrote:
> On Wed, Oct 30, 2013 at 9:24 PM, Chris Arnold
> wrote:
>>
>> Apache/2.2.12 (Linux/SUSE). We have a web app that runs under tomcat
>> (8080). We have apache using mod_proxy (80 and 443). According to the tomcat
>> mailing list:
>
>
>>
>> What
Did you have a trailing slash in the ProxyPass?
I would expect that it would have tried to get /share*/*share/.
- Y
On Thu, Oct 31, 2013 at 10:20 AM, Chris Arnold
wrote:
> On Wed, Oct 30, 2013 at 9:24 PM, Chris Arnold > wrote:
>
>> Apache/2.2.12 (Linux/SUSE). We have a web app that runs under t
On Wed, Oct 30, 2013 at 9:24 PM, Chris Arnold < carn...@electrichendrix.com >
wrote:
Apache/2.2.12 (Linux/SUSE). We have a web app that runs under tomcat (8080). We
have apache using mod_proxy (80 and 443). According to the tomcat mailing list:
What we need is for apache to proxy, rewrit
On Wed, Oct 30, 2013 at 9:24 PM, Chris Arnold
wrote:
> Apache/2.2.12 (Linux/SUSE). We have a web app that runs under tomcat
> (8080). We have apache using mod_proxy (80 and 443). According to the
> tomcat mailing list:
>
> What we need is for apache to proxy, rewrite or whatever the 443 requests
Apache/2.2.12 (Linux/SUSE). We have a web app that runs under tomcat (8080). We
have apache using mod_proxy (80 and 443). According to the tomcat mailing list:
>Do you need
>the application to behave differently given a particular client? If
>not, there's nothing to do. If so, you probably need
22 matches
Mail list logo
