Re: asgard tomcat application 404

Ok guys. Got it! Thanks for your input. I'll follow up with the Asgard list, assuming I can find it. Thanks On Fri, Feb 16, 2018 at 2:40 PM, Olaf Kock wrote: > > On 15.02.2018 23:39, Tim Dunphy wrote: > >> I'm trying to get Netflix Asgard tomcat app working. I'm using

Re: asgard tomcat application 404

On 15.02.2018 23:39, Tim Dunphy wrote: I'm trying to get Netflix Asgard tomcat app working. I'm using tomcat 9. I'm using windows. [...] Tomcat is about as much involved in this as is Windows. To second Christopher's OT answer: This is a problem of the deployed application, not of Tomcat. You

Re: [OT] asgard tomcat application 404

; But when I navigate to /asgard I get a 404 error: > > HTTP Status 404 – Not Found Type Status Report > > Message /asgard/ > > Description The origin server did not find a current representation > for the target resource or is not willing to disclose that one > exists. > >

asgard tomcat application 404

I'm trying to get Netflix Asgard tomcat app working. I'm using tomcat 9. I'm using windows. I can load up the tomcat management and other interfaces no problem. But when I navigate to /asgard I get a 404 error: HTTP Status 404 – Not Found Type Status Report Message /asgard

Re: 404 - servlet not found (7.0.52)

t;> >> >> My >> My >> >> >> and a mapping: >> >> >> My >> /servlet/My >> >> >> >> What I did last was to add another class Mytest in the same directory. >> But it gav

Re: 404 - servlet not found (7.0.52)

in webapps/servlets/WEB-INF/classes/My.class and sections in web.xml for this: My My and a mapping: My /servlet/My What I did last was to add another class Mytest in the same directory. But it gave an error 404 (found later that I forgot

404 - servlet not found (7.0.52)

was to add another class Mytest in the same directory. But it gave an error 404 (found later that I forgot the mapping for that class), deleted the lines for the servlet section for that again . I also deleted ~/work/Catalina and reverted everything back to the old state (where only My

Re: Server giving 404 since upgrade to Tomcat7

gt; >> :-) I'd rather compile from scratch, but that's just the way I was >> brought up. > > Building Tomcat from source is a waste of your time: the official > packages (both from ASF and from Red Hat) have all been built for you > and are environment agnostic. I would never reco

Re: Server giving 404 since upgrade to Tomcat7

mcat from source is a waste of your time: the official > packages (both from ASF and from Red Hat) have all been built for you > and are environment agnostic. I would never recommend that anyone > build Tomcat themselves unless they are trying to hack on it for their > own needs. >

Re: Server giving 404 since upgrade to Tomcat7

t agnostic. I would never recommend that anyone build Tomcat themselves unless they are trying to hack on it for their own needs. Let's try this: 1. Stop Tomcat and remove all log files (or push them somewhere else out of the way) 2. Launch Tomcat (and please tell us how you do that) 3. Make a si

Re: Server giving 404 since upgrade to Tomcat7

was brought up. On 24/07/17 14:50, Coty Sutherland wrote: [...] > In my experience, a 404 after an update (with no other application > changes) suggests that the application failed deployment. Can you > verify that you don't see any exceptions in your log? I would if I knew what to look

Re: Server giving 404 since upgrade to Tomcat7

ing fine for years, through Tomcat and Apache updates. My system owners >> updated the server to Tomcat7 over the weekend and all Tomcat pages re now >> coming up as 404 Not Found. As a temporary fix we have restored service from >> backup on another VM. >> >> The upd

Re: Server giving 404 since upgrade to Tomcat7

r to Tomcat7 over the weekend and all Tomcat pages re now > coming up as 404 Not Found. As a temporary fix we have restored service from > backup on another VM. > > The update was done using the version of Tomcat from the CentOS7 repos > because it is the policy to use the rep

Server giving 404 since upgrade to Tomcat7

coming up as 404 Not Found. As a temporary fix we have restored service from backup on another VM. The update was done using the version of Tomcat from the CentOS7 repos because it is the policy to use the repos only, and I can't change it. It's never been a problem before: Cocoon is the only

Re: [OT] Strange 404 errors

e defined a > context alias in /usr/local/tomcat/conf/context.xml . This is > common practice for many installations I manage, it normally works > 100%. > > Yet here that alias and its content are giving me 404 errors. > > The context alias is called "calllogs"

Strange 404 errors

Hi folks, On a Tomcat 7.0.67 installation on CentOS 7, I have defined a context alias in /usr/local/tomcat/conf/context.xml . This is common practice for many installations I manage, it normally works 100%. Yet here that alias and its content are giving me 404 errors. The context alias

Re: /.well-known Hidden directory url returns 404

d based upon context-path match (e.g. /stats) Tomcat won't check any other application. So if you have application /stats and look for /stats/no-file.html you'll get a 404 even if ROOT/stats/no-file.html exists. > /.well-known/acme-challenge/test.htmlto map to: > www.mydomain.tld/ROOT/.we

Re: /.well-known Hidden directory url returns 404

; serverName=mydomain.tld > serverPort=80 > servletPath=/acme-challenge/test.html > status=404 > > The above fails if /.well-known/acme-challenge/test.html exists or not since > it is looking in the wrong context path. > > Contrasts with a correctly served (not hidden) page. &

Re: /.well-known Hidden directory url returns 404

2017 6:12 PM Subject: Re: /.well-known Hidden directory url returns 404 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ian, On 5/1/17 3:11 PM, Ian Brown wrote: > I am trying to https/SSL enable my tomcat application server and > have a problem when I request verification from the C

Re: /.well-known Hidden directory url returns 404

r you need the ROOT application to respond to those requests. > Request-dumper shows ( some lines removed for clarity) > > requestURI=/.well-known/acme-challenge/test.html > contextPath=/.well-known serverName=mydomain.tld serverPort=80 > servletPath=/acme-challenge/test.html st

Re: /.well-known Hidden directory url returns 404

in exactly how you configured the rewrite. > Request-dumper shows ( some lines removed for clarity) > > requestURI=/.well-known/acme-challenge/test.html > contextPath=/.well-known serverName=mydomain.tld serverPort=80 > servletPath=/acme-challenge/test.html status=404 > &g

/.well-known Hidden directory url returns 404

. Request-dumper shows ( some lines removed for clarity) requestURI=/.well-known/acme-challenge/test.html contextPath=/.well-known serverName=mydomain.tld serverPort=80 servletPath=/acme-challenge/test.html status=404 The above fails if /.well-known/acme-challenge/test.html exists or not since

Re: HTTP 404 error even though Tomcat startup is successful

server.xml: I have deployed 2 .war files (tc.war, tcssoidentity.war & tcssologin.war) on Tomcat. Tomcat manager shows that these 3 are running, but once I click the service, only one of them available. For the other 2, I see message : "The requested resource is not available" with H

HTTP 404 error even though Tomcat startup is successful

, tcssoidentity.war & tcssologin.war) on Tomcat. Tomcat manager shows that these 3 are running, but once I click the service, only one of them available. For the other 2, I see message : "The requested resource is not available" with HTTP Status 404 What could be the reason here ? O

Re: Error 404 - The requested resource is not available

> From: Torsten Krah <krah...@gmail.com> > To: users@tomcat.apache.org, > Date: 13.01.2017 08:56 > Subject: Re: Error 404 - The requested resource is not available > > Am Donnerstag, den 12.01.2017, 13:38 -0600 schrieb fonsin2008 .: > > Here are the log files. &g

Re: Error 404 - The requested resource is not available

Am Donnerstag, den 12.01.2017, 13:38 -0600 schrieb fonsin2008 .: > Here are the log files. What about fixing those NPE and enable debug/trace logs of struts2 to get more information about how struts is going to map the request and where the 404 is written to the respo

Re: Error 404 - The requested resource is not available

, fonsin2008 . wrote: >> >> Hi all! >> >> >> >> First, I need to say that I'm new(ignorant) with Tomcat. One of our >> >> systems is written with tomcat, but today something went wrong and the >> >> following error appears on the webpage:

Re: Error 404 - The requested resource is not available

gt; >> systems is written with tomcat, but today something went wrong and the > >> following error appears on the webpage: > >> > >> --Estado HTTP 404 - /evaluacion/WEB-INF/pages/login/forma_login.jsp > >> --__ > >> --type Informe de estado &

Re: Error 404 - The requested resource is not available

> From: "fonsin2008 ." <fon...@gmail.com> > To: Tomcat Users List <users@tomcat.apache.org>, > Date: 12.01.2017 07:19 > Subject: Re: Error 404 - The requested resource is not available > > Hi! > > The url is: http://somehost/evaluacion/login_form

Re: Error 404 - The requested resource is not available

I need to say that I'm new(ignorant) with Tomcat. One of our >> systems is written with tomcat, but today something went wrong and the >> following error appears on the webpage: >> >> --Estado HTTP 404 - /evaluacion/WEB-INF/pages/login/forma_login.jsp >> --__

Re: Error 404 - The requested resource is not available

On Wed, 2017-01-11 at 15:49 -0600, fonsin2008 . wrote: > Hi all! > > First, I need to say that I'm new(ignorant) with Tomcat. One of our > systems is written with tomcat, but today something went wrong and the > following error appears on the webpage: > > --Estado HTTP 404

Re: Error 404 - The requested resource is not available

stems is written with tomcat, but today something went wrong and the >> following error appears on the webpage: >> >> --Estado HTTP 404 - /evaluacion/WEB-INF/pages/login/forma_login.jsp >> --__ >> --type Informe de estado >> --mensaje

Re: Error 404 - The requested resource is not available

2017-01-11 22:49 GMT+01:00 fonsin2008 . <fon...@gmail.com>: > Hi all! > > First, I need to say that I'm new(ignorant) with Tomcat. One of our > systems is written with tomcat, but today something went wrong and the > following error appears on the webpage: > > --Estado

Re: 404 errors accessing webapp URLs using local IP address on fresh Tomcat 8.5.9 install

; <users@tomcat.apache.org> Sent: Tuesday, January 10, 2017 11:50:27 AM Subject: Re: 404 errors accessing webapp URLs using local IP address on fresh Tomcat 8.5.9 install -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 To whom it may concern, On 1/9/17 12:57 AM, modjkl...@comcast.net wr

Re: 404 errors accessing webapp URLs using local IP address on fresh Tomcat 8.5.9 install

nd line, such as: [root@hostA > ~]# curl -I http://www.example.com/mywebapp/somepage > > it returns status 200 (good). > > Now, if I modify the hostA /etc/hosts file hostA accesses to my > website (www.example.com) on hostB through the cross-connect cable > (e.g. 192.168.0.2

Re: 404 errors accessing webapp URLs using local IP address on fresh Tomcat 8.5.9 install

Message - From: modjkl...@comcast.net To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Sunday, January 8, 2017 9:57:32 PM Subject: 404 errors accessing webapp URLs using local IP address on fresh Tomcat 8.5.9 install I have two Linux servers connected via a cro

404 errors accessing webapp URLs using local IP address on fresh Tomcat 8.5.9 install

(www.example.com) on hostB through the cross-connect cable (e.g. 192.168.0.2 rather than the external IP address), the webpage returns error 404. What can I change to get status 200? My web addresses are xxx.xxx.xxx.xxx (e.g. IPv4). I know Tomcat configures IPv6 by default. So, I modified the setenv.sh

Re: Error 404 for autodiscover.xml

404 anyway - the correct answer. Just like you'll find requests for /robots.txt and /favicon.ico, even if you never reference them anywhere. Olaf Am 14.03.2016 um 08:18 schrieb Subhro Paul: > From: Mark Thomas <ma...@apache.org> > To: Tomcat Users List <users@tomcat.apache.or

Re: Error 404 for autodiscover.xml

From: Mark Thomas <ma...@apache.org> To: Tomcat Users List <users@tomcat.apache.org> Date: 03/11/2016 02:43 PM Subject: Re: Error 404 for autodiscover.xml On 11/03/2016 08:26, Subhro Paul wrote: > Hi All, > > Our client has a simple website consists of s

Re: Error 404 for autodiscover.xml

g we always see the below present in the logs in both > proxy and tomcat box. > > [11/Mar/2016:00:36:04 -0500] "POST /autodiscover/autodiscover.xml > HTTP/1.1" 404 172 > [11/Mar/2016:00:36:06 -0500] "GET /autodiscover/autodiscover.xml HTTP/1.1" > 404 172

Error 404 for autodiscover.xml

:04 -0500] "POST /autodiscover/autodiscover.xml HTTP/1.1" 404 172 [11/Mar/2016:00:36:06 -0500] "GET /autodiscover/autodiscover.xml HTTP/1.1" 404 172 Why this /autodiscover/autodiscover.xml is called? Who is calling it? Is that a feature of Apache proxy which is automatically c

Re: Tomcat 8.0.30 silently transforms 302 into 404

ive URLs. > > Before 8.0.30 a redirect URL string was simply returned to the client. Now > it has to be a valid URI (not URL) for the response to succeed. > If URI.create() fails, no error message is given or exception is thrown. > Tomcat just sets the response code to 404. > >

Tomcat 8.0.30 silently transforms 302 into 404

(not URL) for the response to succeed. If URI.create() fails, no error message is given or exception is thrown. Tomcat just sets the response code to 404. This behavior was introduced in revision 1717256. I appreciate stricter rules in this point, but please consider throwing a RuntimeException

Re: Very Strange 404 to JSP with getRequestDispatcher().forward()

2015-12-24 18:12 GMT+03:00 Marc Boorshtein : >> >> You have to provide the actual source code. >> >> There is an example in the examples webapp that performs forwarding to >> a JSP and it works, >> >> \webapps\examples\WEB-INF\classes\ServletToJsp.java >> >> > So the good

Re: Very Strange 404 to JSP with getRequestDispatcher().forward()

> > > > Your request wrappers store their own reference to a > HttpServletRequest in addition to the one stored by the > ServletRequestWrapper class. > > > My guess is that your issue will be solved if you either override > ServletRequestWrapper.setRequest() to update your request field, or > use

Very Strange 404 to JSP with getRequestDispatcher().forward()

All, I'm having a very strange issue with request.getServletContext().getRequestDispatcher().forward(). It gives me a 404 on a JSP page that if I go to directly, works fine. This is with tomcat 8.0.30 on OSX on JDK : ava version "1.7.0_65" Java(TM) SE Runtime Environment (build 1.

Re: Very Strange 404 to JSP with getRequestDispatcher().forward()

2015-12-24 17:37 GMT+03:00 Marc Boorshtein <mboorsht...@gmail.com>: > All, > > I'm having a very strange issue with > request.getServletContext().getRequestDispatcher().forward(). It gives me > a 404 on a JSP page that if I go to directly, works fine. This is with > tom

Re: Very Strange 404 to JSP with getRequestDispatcher().forward()

> > You have to provide the actual source code. > > There is an example in the examples webapp that performs forwarding to > a JSP and it works, > > \webapps\examples\WEB-INF\classes\ServletToJsp.java > > So the good news is that I got it to work by getting rid of any of the methods that were

Error during WebSocket handshake: Unexpected response code: 404

Hi all, I’m trying make Websockets work with embedded Tomcat (8.0.28) started by Main class (shown below). When I try to open websocket connection from browser using the URLs below, I always get “Error during WebSocket handshake: Unexpected response code: 404”. Is there anything wrong

Tomcat returning error 404 for any file but index.html

). I know there are a list of welcome files in web.xml such as welcome-file-list> index.html . Even including for example the index_backup.html in the welcome-file-list it returns 404 - The requested resource is not available. I've chec

Re: 404 during application redeploying

On 07/08/2015 10:00, Pavel Cibulka wrote: Hi, I'm using Tomcat 8.0.23 on Ubuntu 14.04. When I redeploy application (by replacing WAR file), tomcat returns 404 for short period of time. Is this intended? Yes. I have found in: https://bz.apache.org/bugzilla/show_bug.cgi?id=53024 Bug 53024

404 during application redeploying

Hi, I'm using Tomcat 8.0.23 on Ubuntu 14.04. When I redeploy application (by replacing WAR file), tomcat returns 404 for short period of time. Is this intended? I have found in: https://bz.apache.org/bugzilla/show_bug.cgi?id=53024 Bug 53024 - Accessing Servlet while Reloading context gives 404

Re: 404 during application redeploying

(by replacing WAR file), tomcat returns 404 for short period of time. Is this intended? Yes. I have found in: https://bz.apache.org/bugzilla/show_bug.cgi?id=53024 Bug 53024 - Accessing Servlet while Reloading context gives 404 error Mark Thomas 2012-05-08 19:08:09 UTC Thanks for the test

Accessing static resources return 404 in embedded tomcat

/ * Context docBase=/home/thusitha/abc path=/test/res / * I have an empty xml file in the /home/thusitha/abc folder. On the browser when I try to access it as follows I'm getting 404 error. localhost:9443/test/res/abc.xml What could be the reason for this? Thanks Best Regards --

Re: CGIServlet - Disregarding 404 error-page

as a servlet init-param to allow support for the error-pages. The default would maintain current functionality so as not to break anything currently in place. Something like: if (!cgiEnv.isValid()) { if (shouldTriggerErrorPage) { res.sendError(404

Re: CGIServlet - Disregarding 404 error-page

2015-03-16 21:52 GMT+03:00 Jacob Haverkost jdh5...@gmail.com: Version: 6.0.43 OS: Win7 x64 Currently, the CGIServlet does not appear to support using the 404 error-page specified in the web.xml (ROOT). The error-pages work fine This appears to be due to the line, res.setStatus(404);, inside

CGIServlet - Disregarding 404 error-page

Version: 6.0.43 OS: Win7 x64 Currently, the CGIServlet does not appear to support using the 404 error-page specified in the web.xml (ROOT). The error-pages work fine This appears to be due to the line, res.setStatus(404);, inside of doGet(). According to the documentation

Re: CGIServlet - Disregarding 404 error-page

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jacob, On 3/16/15 2:52 PM, Jacob Haverkost wrote: Version: 6.0.43 OS: Win7 x64 Currently, the CGIServlet does not appear to support using the 404 error-page specified in the web.xml (ROOT). The error-pages work fine This appears to be due

Re: tomcat 8.0.20 can't make manager run HTTP Status 404 - /manager/status etc

404 1022 http://localhost:8080/manager/html returns 127.0.0.1 - - [26/Feb/2015:11:00:40 -0500] GET /manager/html HTTP/1.1 404 1018 This works for me. What client are you using? Just a web browser? The 404 seems odd. I am starting tomcat 8.0.20 with jsvc and running tomcat as mas

tomcat 8.0.20 can't make manager run HTTP Status 404 - /manager/status etc

This is truly embarrassing since I have the manager running fine on tomcat 7. http://localhost:8080/manager/status returns 127.0.0.1 - - [26/Feb/2015:10:47:11 -0500] GET /manager/status HTTP/1.1 404 1022 http://localhost:8080/manager/html returns 127.0.0.1 - - [26/Feb/2015:11:00:40 -0500] GET

Re: tomcat 8.0.20 can't make manager run HTTP Status 404 - /manager/status etc

=t8sx2oxLU2xFh_hEfhXwWU4fIqfFYmqPF9q4PmUBS_Qs=oRaGhibZvAOGCqQay4tltXaYNS7R8Coq6rBIG-D3CEke= returns 127.0.0.1 - - [26/Feb/2015:10:47:11 -0500] GET /manager/status HTTP/1.1 404 1022 https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8080_manager_htmld=AwIC-gc=-dg2m7zWuuDZ0MUcV7Sdqwr

Re: tomcat 8.0.20 can't make manager run HTTP Status 404 - /manager/status etc

=-dg2m7zWuuDZ0MUcV7Sdqwr=oZj4zInar3jeBECJ7OuBEMWJwBrzGeex-klf3JCRGssm=qAAyZ6f2PpvD8ZHfq17E7vm0di_oOBZ5L417zIFArJos=CKor4EvRLf9Xl_PoOL58dKcTnpRepmn-UxWIo91RQJMe= returns 127.0.0.1 - - [26/Feb/2015:10:47:11 -0500] GET /manager/status HTTP/1.1 404 1022 https://urldefense.proofpoint.com/v2/url?u=http

Re: tomcat 8.0.20 can't make manager run HTTP Status 404 - /manager/status etc

2015-02-26 19:26 GMT+03:00 Mark Shifman mark.shif...@yale.edu: This is truly embarrassing since I have the manager running fine on tomcat 7. http://localhost:8080/manager/status returns 127.0.0.1 - - [26/Feb/2015:10:47:11 -0500] GET /manager/status HTTP/1.1 404 1022 http://localhost:8080

Http Status 404

Hye I am using Tomcat 8.0.1 ,my operating system is Windows 8.1 and it is 64- bit configuration .I made a folder in webapps for my servlet but I am unable to access it Please help

Re: Http Status 404

On 06/02/2014 08:57, Shivam Mishra wrote: Hye I am using Tomcat 8.0.1 ,my operating system is Windows 8.1 and it is 64- bit configuration .I made a folder in webapps for my servlet but I am unable to access it Please help Read this: http://www.catb.org/~esr/faqs/smart-questions.html then post

Re: Http Status 404

On Feb 6, 2014 9:58 AM, Shivam Mishra shmishra...@gmail.com wrote: Hye I am using Tomcat 8.0.1 ,my operating system is Windows 8.1 and it is 64- bit configuration .I made a folder in webapps for my servlet but I am unable to access it Please help Shivam, Is your tomcat running? What port

Re: Http Status 404

My tomcat and its example application is running but I got an error with my own application .My port number is 8080 .I compile my servlet programme in jdk 7 .and my web.xml file is below ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web

Re: Http Status 404

On Feb 6, 2014 4:21 PM, Shivam Mishra shmishra...@gmail.com wrote: My tomcat and its example application is running but I got an error with my own application .My port number is 8080 .I compile my servlet programme in jdk 7 .and my web.xml file is below ?xml version=1.0 encoding=ISO-8859-1?

Re: Http Status 404

On Thu, 2014-02-06 at 10:32 -0500, Neven Cvetkovic wrote: On Feb 6, 2014 4:21 PM, Shivam Mishra shmishra...@gmail.com wrote: My tomcat and its example application is running but I got an error with my own application .My port number is 8080 .I compile my servlet programme in jdk 7 .and

Re: Http Status 404

My directory structure is C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\name\WEB-INF\Classes for .class file of Servlet Description of my logs is below 06-Feb-2014 14:50:22.684 INFO [Thread-9] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler [http-nio-8080]

Re: Http Status 404

On Thu, 2014-02-06 at 21:32 +0530, Shivam Mishra wrote: My directory structure is C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\name\WEB-INF\Classes for .class file of Servlet That last part should be ...\WEB-INF\classes (lower case 'c'). If that doesn't fix it then, again I

Re: Http Status 404

My url is http://localhost:8080/name/TestServlet On Thu, Feb 6, 2014 at 10:55 PM, Tim Watts t...@cliftonfarm.org wrote: On Thu, 2014-02-06 at 21:32 +0530, Shivam Mishra wrote: My directory structure is C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\name\WEB-INF\Classes for

Re: Http Status 404

Now my browser is showing this error as below: Exception report *message* *Error instantiating servlet class TestServlet* *description* *The server encountered an internal error that prevented it from fulfilling this request.* *exception* javax.servlet.ServletException: Error instantiating

Re: Http Status 404

On Thu, 2014-02-06 at 23:07 +0530, Shivam Mishra wrote: Now my browser is showing this error as below: Exception report *message* *Error instantiating servlet class TestServlet* *description* *The server encountered an internal error that prevented it from fulfilling this request.*

Re: Http Status 404

Its running thank you very much ... On Thu, Feb 6, 2014 at 11:24 PM, Tim Watts t...@cliftonfarm.org wrote: On Thu, 2014-02-06 at 23:07 +0530, Shivam Mishra wrote: Now my browser is showing this error as below: Exception report *message* *Error instantiating servlet class

Re: Http Status 404

On Thu, Feb 6, 2014 at 11:02 AM, Shivam Mishra shmishra...@gmail.comwrote: My directory structure is C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\name\WEB-INF\Classes for .class file of Servlet That should probably be lowercase classes, e.g. C:\Program Files\Apache

Re: Http Status 404

On 2/6/2014 1:05 PM, Shivam Mishra wrote: Its running thank you very much ... Can you tell us what the trouble was, so other people with the same issue can learn from it? On Thu, Feb 6, 2014 at 11:24 PM, Tim Watts t...@cliftonfarm.org wrote: On Thu, 2014-02-06 at 23:07 +0530, Shivam

Re: Http Status 404

I did not make the TestServlet class public . On Fri, Feb 7, 2014 at 12:05 AM, David kerber dcker...@verizon.net wrote: On 2/6/2014 1:05 PM, Shivam Mishra wrote: Its running thank you very much ... Can you tell us what the trouble was, so other people with the same issue can learn from

Re: Getting 404 before the container starts all servlets

On 10/01/2014 23:08, Adrian Tarau wrote: I tried with 7.0.47 and I still get 404 regardless of the the state of bindOnInit. Tomcat doesn't serve *any* requests until everything (including applications) has started up. bindOnInit only controls when it starts accepting connections. You should

Re: exception-message header reveals path to document root in 404 response.

On 11/01/2014 00:02, Caldarale, Charles R wrote: From: August Kleimo [mailto:aug...@kleimo.com] Subject: exception-message header reveals path to document root in 404 response. I'm failing a PCI compliance scan because my Tomcat Version 7.0.20 server is revealing the path to the document

Re: Getting 404 before the container starts all servlets

On Sat, Jan 11, 2014 at 4:40 AM, Mark Thomas ma...@apache.org wrote: On 10/01/2014 23:08, Adrian Tarau wrote: I tried with 7.0.47 and I still get 404 regardless of the the state of bindOnInit. Tomcat doesn't serve *any* requests until everything (including applications) has started up

Re: exception-message header reveals path to document root in 404 response.

On Fri, Jan 10, 2014 at 7:02 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: Here's Tomcat's standard 404 response: HTTP/1.1 404 Not Found Server: Apache-Coyote/1.1 Content-Type: text/html;charset=utf-8 Content-Length: 1027 Date: Fri, 10 Jan 2014 23:59:34 GMT Wow, when I saw

RE: exception-message header reveals path to document root in 404 response.

From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] Subject: Re: exception-message header reveals path to document root in 404 response. Wow, when I saw this last night, I shook my head and said to myself, Server: Apache-Coyote/1.1 this may be one of the reasons why my server/web

Re: exception-message header reveals path to document root in 404 response.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 August, On 1/10/14, 7:48 PM, August Kleimo wrote: Hi All, Thanks for all your replies. Turns out it was in fact Railo. I searched the Railo repo on GitHub and found a reference to that header. I was able to overwrite it with a blank string

Re: exception-message header reveals path to document root in 404 response.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chuck, On 1/11/14, 9:01 AM, Caldarale, Charles R wrote: From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] Subject: Re: exception-message header reveals path to document root in 404 response. Wow, when I saw this last night, I shook

Re: exception-message header reveals path to document root in 404 response.

On Sat, Jan 11, 2014 at 9:01 AM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] Subject: Re: exception-message header reveals path to document root in 404 response. Wow, when I saw this last night, I shook my head

Re: Getting 404 before the container starts all servlets

Mark, Thank you for your response. The same application started under 6.0 does not manifest itself like that. The first thing that I did was to put a break point in the first filter, to see if the 404 comes from one of the servlets. I got a 404 without reaching any the break point. I

Re: Getting 404 before the container starts all servlets

404 before the container starts all servlets After upgrading Tomcat from 6.X to 7.X, our AJAX client receives 404 for 10-15 seconds right after startup. I presume the request is accepted and processed before all servlet are initialized, which is not what you would expect. Is this behavior normal for 7

RE: Getting 404 before the container starts all servlets

From: Adrian Tarau [mailto:mailingl...@adrian.tarau.org] Subject: Re: Getting 404 before the container starts all servlets I tried with bindOnInit=false and bindOnInit=true, it makes no difference. I'm using tomcat 7.0.34, would this option be available in 7.0.34? It should be. Note

Re: Getting 404 before the container starts all servlets

I tried with 7.0.47 and I still get 404 regardless of the the state of bindOnInit. /Connector port=8080 protocol=HTTP/1.1// // connectionTimeout=2// // redirectPort=8443 bindOnInit=false/true// On 01/10/2014 01:38 PM, Caldarale, Charles R wrote: From: Adrian

“exception-message” header reveals path to document root in 404 response.

of Tomcat ... but I think this header is coming from Tomcat. $ curl -I http://mydomain.com/this-page-does-not-exist.html HTTP/1.1 404 Not Found Date: Fri, 10 Jan 2014 23:23:22 GMT Server: Apache-Coyote/1.1 exception-message: Page /this-page-does-not-exist.html [/var/www/html/this-page-does

Re: “exception-message” header reveals path to document root in 404 response.

the response? Note: I'm running Railo 4.1.2 on top of Tomcat ... but I think this header is coming from Tomcat. $ curl -I http://mydomain.com/this-page-does-not-exist.html HTTP/1.1 404 Not Found Date: Fri, 10 Jan 2014 23:23:22 GMT Server: Apache-Coyote/1.1 exception-message: Page /this-page-does

RE: exception-message header reveals path to document root in 404 response.

From: August Kleimo [mailto:aug...@kleimo.com] Subject: exception-message header reveals path to document root in 404 response. I'm failing a PCI compliance scan because my Tomcat Version 7.0.20 server is revealing the path to the document web root in an exception-message header when

Re: “exception-message” header reveals path to document root in 404 response.

/this-page-does-not-exist.html HTTP/1.1 404 Not Found Date: Fri, 10 Jan 2014 23:23:22 GMT Server: Apache-Coyote/1.1 exception-message: Page /this-page-does-not-exist.html [/var/www/html/this-page-does- not-exist.html] not found Content-Type: text/html;charset=UTF-8 Content-Length: 44 Set

Re: exception-message header reveals path to document root in 404 response.

install and install a Railo war? Have you customized your install at all or added any custom configs? Warm Regards, Jordan Michaels On 01/10/2014 04:02 PM, Caldarale, Charles R wrote: From: August Kleimo [mailto:aug...@kleimo.com] Subject: exception-message header reveals path to document root in 404

Re: exception-message header reveals path to document root in 404 response.

It may also be useful to know if you get this same exception-message header when you get a 404 from the Railo servlet (from a request for a .cfm file). It may help determine if Railo is involved or not. Warm Regards, Jordan Michaels On 01/10/2014 04:02 PM, Caldarale, Charles R wrote: From

Re: exception-message header reveals path to document root in 404 response.

, Jan 10, 2014 at 4:36 PM, Jordan Michaels jor...@viviotech.netwrote: It may also be useful to know if you get this same exception-message header when you get a 404 from the Railo servlet (from a request for a .cfm file). It may help determine if Railo is involved or not. Warm Regards

Re: exception-message header reveals path to document root in 404 response.

string using this line of code. cfset getPageContext().getResponse().setHeader(exception-message,) On Fri, Jan 10, 2014 at 4:36 PM, Jordan Michaels jor...@viviotech.netwrote: It may also be useful to know if you get this same exception-message header when you get a 404 from the Railo servlet

Getting 404 before the container starts all servlets

Hello, After upgrading Tomcat from 6.X to 7.X, our AJAX client receives 404 for 10-15 seconds right after startup. I presume the request is accepted and processed before all servlet are initialized, which is not what you would expect. Is this behavior normal for 7.X? Is there a way

RE: Getting 404 before the container starts all servlets

From: Adrian Tarau [mailto:mailingl...@adrian.tarau.org] Subject: Getting 404 before the container starts all servlets After upgrading Tomcat from 6.X to 7.X, our AJAX client receives 404 for 10-15 seconds right after startup. I presume the request is accepted and processed before all

<    1   2   3   4   5   6   7   8   9   10   >