On 2/3/2016 12:23 PM, prashant sharma wrote:
On 3 Feb 2016 16:38, "Mark Eggers" <its_toas...@yahoo.com.invalid> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quick note - please post at the bottom or inline.
See item 6 of the Tomcat users mailing list here:
http://tomcat.apache.org/lists.html
On 2/3/2016 8:20 AM, prashant sharma wrote:
That's true. But we are not doing any authn/authz in our
application. Its just a simple webapp that exposes 1 endpoint (put
method). Any body should be able to hit that end point.
It works fine if I place my war outside tomcat installation
directory and create a context from Catalina/localhost. But if I
place my war inside webapps then it gives http 403 when I hit my
endpoint.
Regards, Prashant
07440456543 On 3 Feb 2016 16:11, "David kerber"
<dcker...@verizon.net> wrote:
403 is an authentication/authorization error, which means the
logged-in user doesn't have permissions to the requested
resource.
On 2/3/2016 11:05 AM, prashant sharma wrote:
Hi, Can someone pls provide any inputs on below. Thanks
Regards, Prashant
07440456543 On 2 Feb 2016 18:02, "prashant sharma"
<pacificmist.0...@gmail.com> wrote:
Hi,
I am using apache tomcat 7.0.57 and jdk 7 on windows 7. I
have deployed a simple web application inside tomcat webapps
folder by placing the war file directly in webapps. This is a
basic application which exposes an endpoint with put request
method.
When I try to access this endpoint I get 403 access forbidden
error.
However If I place war file outside tomcat and point it by
creating context.xml in conf/Catalina/localhost I am able to
access my endpoint.
Can someone pls tell what's wrong with the first approach and
why its not working in that
Regards, Prashant
07440456543
With your put method, are you trying to write to a file within the web
application?
. . . just my two cents
This put method updates a record in database.
The same webapp(endpoint) works when I place war outside tomcat.
Check the permissions on the directories where you are placing the .war
file.
/mde/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJWsiy6AAoJEEFGbsYNeTwtQl8IAJyMU5CIE5ex3QTLbnnEzM/P
SCPTn6yTFnMleBtKpKHpiVsc2pc3ebXaSWsWqTId6ahGbDnl6bGUewKfGU/ybeqr
9gxYNj75d3z2xHFaOiVZjf67zGgS7pQ+XUSlIrogrsVQ5mDopRGgdkDsUPnerdlL
w0288AGjnh9IKMXJ3MiFK3qORImjIEINTLDpnAcdoX5fbGwkVKyIF74VNrH2xqot
zI0fglepGn9bk8MB1r+JkRVnrFwhXjfwhCBREnf8+Uy4LrszEF8CVmvNVsAQLxm1
9d6cOPLO4rGv/UGBCrK596vXQOQZ+hg1NpN04Gfd5evLafI0x29bE7AYFmcxKPo=
=ZL/3
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
