Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of gadi.sastiel@gmail.com
 designates 209.85.223.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <542AFF20.3060909@ice-sa.com>
References: 
 <CAJgo4M8521fbvd9ipAzBEPP-zDi0D18wToAjcCpvfVUpzpo8OQ@mail.gmail.com>
	<CABzHfV=6bS4JAehYL1O4PH3Ys7k4oVBsq31bR2PAX0Ffy2OEmw@mail.gmail.com>
	<CAJgo4M86TRik_0qeYthd=_Z6egeNTm+9jT5owzua7KLHDu-pQA@mail.gmail.com>
	<CAAqVxAx3-D56Fqg4tG1Ns7cqCJVh+nO_QfqRrDCsSv4PRTQMYw@mail.gmail.com>
	<CAJgo4M-N2V5AXamvKzv4Yie=ATe6eA08ykV=CSah89hbszwzpw@mail.gmail.com>
	<542AFF20.3060909@ice-sa.com>
Date: Wed, 1 Oct 2014 10:14:48 +0300
Message-ID: 
 <CAJgo4M8jX9FjmvadbLZvU6NXVrUPA4ToQ2aAro28gZfCkv8mQQ@mail.gmail.com>
Subject: Re: Tomcat returns Jsp source code as text/plain to the browser
From: Gadi Sastiel <gadi.sastiel@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=90e6ba614f0a5a00a80504574151

--90e6ba614f0a5a00a80504574151
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, the request is seen on the tomcat access log ( i've changed the
path deliberately)

[01/Oct/2014:10:01:27 +0300] "GET /xxxxx/yyyyyy/zzzzz/aaaaPage.jsp%22
HTTP/1.1" 200 30223

Thanks
Gadi

On Tue, Sep 30, 2014 at 10:06 PM, Andr=C3=A9 Warnier <aw@ice-sa.com> wrote:

> Gadi Sastiel wrote:
>
>> I have in httpd.conf:
>>
>> LoadModule proxy_module modules/mod_proxy.so
>> LoadModule proxy_http_module modules/mod_proxy_http.so
>>
>> # Configure mod_proxy_html to understand HTML4/XHTML1
>> <IfModule proxy_html_module>
>> Include conf/extra/proxy-html.conf
>> </IfModule>
>>
>> LoadModule jk_module modules/mod_jk.so
>>
>> Gadi
>>
>
> Maybe to gain some time, let me point you to the explanation of what both
> Konstantin and Daniel are looking for :
> https://tomcat.apache.org/connectors-doc/reference/apache.html
> See the text in red ?
>
> In more words : a frequent configuration error in such cases (where Apach=
e
> httpd in a front-end for Tomcat, and both are on the same machine), is to
> allow Apache httpd to "see" the contents of the Tomcat application
> directories (/webapps/*).
> Tomcat "knows" that a JSP page is something which has to be processed, an=
d
> that it is the result that should be returned to the client, not the sour=
ce.
> But httpd doesn't know that, and for him a JSP page is just text, and it
> returns it as is.
>
> So if the URL of the request is such, that Apache does not think that thi=
s
> request has to be forwarded to Tomcat, it will try to process this reques=
t
> itself.  And if it can do that (aka it sees the directory where this file
> is located, and the file in it), then it will return that page itself to
> the client, as text.
>
> And that seems to be what you are seeing.  From there comes the suspicion
> of Konstantin and Daniel, because Tomcat, correctly configured, wouldn't =
do
> that.
>
> Except that you mention somwhere else that the request is visible in the
> Tomcat access log.  That would normally mean that httpd /is/ forwarding
> this request to Tomcat, and that the error is on the Tomcat side.  So
> before going any further, make absolutely sure that that is the case, and
> that it is really /this/ request that you are seeing in the tomcat logs.
> Otherwise everyone is going to lose a lot of time searching in the wrong
> places.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

--90e6ba614f0a5a00a80504574151--