On 27/05/2014, at 6:09 am, Christopher Schultz
wrote:
>
> If you run the code I referenced elsewhere in this thread, you'll see
> that some of the components are available, just not in the
> combinations you have above:
>
> $ java -showversion -classpath build/ SSLInfo | grep '\(256\|384\)'
On 26/05/2014, at 6:58 pm, Sverre Moe wrote:
>> Documentation aside, none of these cipher-suites are supported in Oracle
> Java 7.
> The AES_CBC ciphers I had there are supported in Java 7.
>
> I have already concluded as much regarding the AES_x_GCM. Using Java 8 one
> have access to these hig
On 21/05/2014, at 10:21 pm, Sverre Moe wrote:
> ciphers="TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA265,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA256"
> />
Documentation aside, none of these cipher-suites are supported in Oracle J
On Tue, Feb 19, 2013 at 10:59 AM, Giuseppe Sacco
wrote:
[...]
> I listed all providers here:
> http://centrum.lixper.it/~giuseppe/ipad-tomcat-list-ciphers-no-bouncycastle.html
> as you may see, a few of them are TLS_RSA and TLS_DHE:
> * TLS_RSA_WITH_AES_128_CBC_SHA
> * TLS_RSA_WITH_AE
>>As can be seen from your usage of "keystoreType" attribute, you are
>>using Java implementation of the Connector, not openssl/APR one.
>>
>>You should look into Java documentation for their cipher names.
>>
>>See this thread from October 2009:
>>http://markmail.org/message/zn4namfhypyxum23
>
> A
It looks like this is a regression in 1.2.31 - the socket shutdown
code that drained the response message from the AJP socket before
closing it was mis-counting the bytes read, causing a CPU busy loop
until it hit a 30 second cap on lingering byte reads.
I've committed a fix for 1.2.32 and also ca
This sounds like https://issues.apache.org/bugzilla/show_bug.cgi?id=50839
If you can capture a TRACE level log form the Tomcat Connector
(configure in isapi_redirect.properties) and attach it to the bug,
I'll take a look.
cheers
tim
On Sun, May 15, 2011 at 1:20 AM, eurotrans-Verlag
wrote:
> Hel
Start at org.apache.tomcat.util.net.AbstractEndpoint.createExecutor()
and follow your nose from there.
If you make any progress and want to discuss implementation details,
then the dev list is the best place to discuss those.
cheers
tim
On Mon, Apr 11, 2011 at 11:34 PM, Pid wrote:
> On 4/10/11 5
On Mon, Mar 28, 2011 at 7:26 AM, Stefan Mayr wrote:
> Hello everybody,
>
> as many others before we wanted to do single-sign-on for intranet web
> applications using integrated windows authentication (negotiate because IE
> sometimes tries NTLM instead of using plain kerberos - breaking all our
>
gi?id=50363
cheers
tim
On Mon, Nov 29, 2010 at 11:10 PM, Tim Whittington wrote:
>> This is the first time I ask a question here, so I hope I do it right.
>>
>> I am using Tomcat 7.0.5 (with Tomcat Native 1.1.20 library) on Windows
>> Server 2003 (32-Bit) with Java 1.
> This is the first time I ask a question here, so I hope I do it right.
>
> I am using Tomcat 7.0.5 (with Tomcat Native 1.1.20 library) on Windows
> Server 2003 (32-Bit) with Java 1.6.0_22, and I have configured IIS6.0 to use
> the Jakarta 1.2.31 ISAPI Redirector (with "enable_chunked_encoding" se
Welcome aboard.
tim
On Tue, Nov 23, 2010 at 8:16 AM, Mark Thomas wrote:
> On behalf of the Tomcat committers I am pleased to announce that
> Christopher Schultz (schultz) has been voted in as a new Tomcat committer.
>
> Please join me in welcoming him.
>
> Mark
>
> --
mod_jk does chunked encoding on all dynamic responses (e.g. From Tomcat)
that don¹t already have some form of response end set (e.g. A Content-Length
header).
To be accurate I think this is more a function of Apache than mod_jk.
All you should need to do is connect Tomcat to Apache using mod_jk and
It looks like you've got more than one thing going on.
The debug log refers to a worker named 'ajp13', which is the default name,
and not the one you've got configured in your
uriworkermap.properties/worker.properties
- This usually points to your filter config and the ISAPI extension DLL
(the o
That log statement indicates you haven't enabled chunked encoding in the
connector config (it's off by default).
Add enable_chunked_encoding=true to your isapi_redirect.properties (or as
a registry setting if you're using that) and restart IIS.
tim
-Original Message-
From: Woytasik Joe [m
>From what I can tell there's nothing (technically) wrong with what Tomcat
+ ISAPI Redirector is doing here.
What's actually happening here is that Tomcat internally only provides a
Content-Length header if it can determine the length of the content easily
(e.g. it's a static file) or the Servlet
Binary builds of 1.2.26 for various platforms are available now from
http://sourceforge.net/projects/timsjk/
These include builds of a patched IIS 5/6 ISAPI Redirector that support
HTTP 1.1 chunked encoding (and thus keep-alives on dynamic content).
cheers
tim
-Original Message-
From: Ra
e any insight on
this? :)
-Travis Haagen
----- Original Message -
From: "Tim Whittington" <[EMAIL PROTECTED]>
To: ; <[EMAIL PROTECTED]>
Sent: Thursday, December 20, 2007 5:20 PM
Subject: [Announce] Enhanced ISAPI Redirector + Tomcat Connector Binaries
> Hi all
>
Hi all
We've been using Tomcat and Tomcat Connectors in our company products for
almost 10 years now, and it's a very important part of our technology stack.
Over those years we've contributed some enhancements and fixes to the IIS
connector/ISAPI Redirector, and most of these have been accepted
19 matches
Mail list logo
