2014/1/11 Jeffrey Janner :
> Tomcat 7 did a good job of collecting all the new Microsoft mime types into
> the standard web.xml file, but missed the mapping for the ".one" file type
> for OneNote, even though that's fully documented on the Microsoft Mime Types
> page.
1. What page, exactly?
>
Thanks August, good to know.
Warm Regards,
Jordan Michaels
On 01/10/2014 04: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 stri
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 using this line of code.
On Fri, Jan 10, 2014 at 4:36 PM, Jordan Michaels wrote:
> It may also be
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:
Although I suppose it's possible, I don't think it has to do with Railo.
The Railo servlet doesn't handle requests for .html files... those are
handled by Tomcat's default servlet.
Here are the default (suggested) handlers for a Railo install:
CFMLServlet
*.cfm
*.c
Thanks, Perhaps it's coming from Railo then. I'll investigate down that
path.
On Fri, Jan 10, 2014 at 3:56 PM, Mark Eggers wrote:
> On 1/10/2014 3:28 PM, August Kleimo wrote:
>
>> I'm failing a PCI compliance scan because my Tomcat Version 7.0.20 server
>> is revealing the path to the document
> 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
On 1/10/2014 3:28 PM, August Kleimo wrote:
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 a missing page is requested.
Does anyone know of way to get rid of this header from the respon
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 a missing page is requested.
Does anyone know of way to get rid of this header from the response?
Note: I'm running Railo 4.1.2 on top of
I tried with 7.0.47 and I still get 404 regardless of the the state of
bindOnInit.
//
On 01/10/2014 01:38 PM, Caldarale, Charles R wrote:
From: Adrian Tarau [mailto:mailingl...@adrian.tarau.org]
Subject: Re: Getting 404 before the container starts all servlets
I tried with bindOnInit=false and
On 1/10/2014 2:53 PM, Alex Lucard wrote:
.
On Jan 10, 2014 5:00 PM, "Alex Lucard" wrote:
I am running CentOS 6.5 and tomcat 7
I cannot get the mod_jk to work
I have a JSP page on this server and if you go to localhost:8080/Hello it
will work but if I just go to localhost/Hello The requested UR
.
On Jan 10, 2014 5:00 PM, "Alex Lucard" wrote:
> I am running CentOS 6.5 and tomcat 7
> I cannot get the mod_jk to work
> I have a JSP page on this server and if you go to localhost:8080/Hello it
> will work but if I just go to localhost/Hello The requested URL /Hello was
> not found on this ser
Tomcat 7 did a good job of collecting all the new Microsoft mime types into the
standard web.xml file, but missed the mapping for the ".one" file type for
OneNote, even though that's fully documented on the Microsoft Mime Types page.
The entry is:
one
application/onenote
I know
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Thursday, January 09, 2014 4:08 PM
> To: Tomcat Users List
> Subject: Re: Question on SSL and Pragma in 7.x
>
> On 09/01/2014 18:22, Jeffrey Janner wrote:
> > I'd like to verify something I think I'm seeing in Tomca
> 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
Hi
Am 09.01.2014 14:21, schrieb Divyaprakash Y:
-Original Message-
From: Divyaprakash Y
Sent: 08 January 2014 14:35
To: Tomcat Users List
Subject: RE: Packet misses in Tomcat
-Original Message-
From: André Warnier [mailto:a...@ice-sa.com]
Sent: 08 January 2014 02:52
To: Tomcat
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?
Thanks,
Adrian Tarau.
On 01/09/2014 11:19 PM, Caldarale, Charles R wrote:
From: Adrian Tarau [mailto:mailingl...@adrian.tarau.org]
Subject: Getting 404
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nancee,
On 1/10/14, 5:28 AM, Nancee Riehl wrote:
> thank you for your reply! On the tomcat everything works fine, I
> can see that the client certificate is checked via my
> JSSE-Implementation in both cases!
>
> This is the stacktrace from my test
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: 10 January 2014 03:46
To: Tomcat Users List
Subject: Re: Packet misses in Tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Divyaprakash,
On 1/8/14, 4:06 AM, Divyaprakash Y wrote:
> -Origi
Hi Chris,
thank you for your reply!
On the tomcat everything works fine, I can see that the client certificate
is checked via my JSSE-Implementation in both cases!
This is the stacktrace from my test:
java.net.SocketException: Software caused connection abort: socket write
error
at java.net.Sock
20 matches
Mail list logo