RE: Does Tomcat/Java get around the problem of 64K maximum client source ports?

2020-03-27 Thread Eric Robinson
Thanks for all the feedback, André, Christopher, and John. Let me see if I can quickly answer everyone's comments. Since there is a TCB for each connection, and the OS knows which TCBs are associated with which processes, I don't see any problem using the same local port on different sockets.

Re: Practical multipart handling

2020-03-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 3/27/20 14:46, Christopher Schultz wrote: > Mark, > > On 3/27/20 13:35, Mark Thomas wrote: >> On 27/03/2020 15:52, Christopher Schultz wrote: >>> On 3/26/20 18:44, Konstantin Kolinko wrote: > >> > I think that those are available via

Re: Practical multipart handling

2020-03-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 3/27/20 13:35, Mark Thomas wrote: > On 27/03/2020 15:52, Christopher Schultz wrote: >> On 3/26/20 18:44, Konstantin Kolinko wrote: > > > >>> I think that those are available via the standard >>> request.getParameter(name) API. >> >> That

Re: Does Tomcat/Java get around the problem of 64K maximum client source ports?

2020-03-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 3/27/20 11:01, André Warnier (tomcat/perl) wrote: > On 27.03.2020 14:27, André Warnier (tomcat/perl) wrote: >> On 26.03.2020 20:42, Eric Robinson wrote: -Original Message- From: Olaf Kock Sent: Thursday, March 26, 2020

Re: Does Tomcat/Java get around the problem of 64K maximum client source ports?

2020-03-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 John, On 3/27/20 13:37, john.e.gr...@wellsfargo.com.INVALID wrote: > A few random thoughts. > > First, this is really a MySQL driver thing, not a Tomcat thing. > If you want to know why the driver does what it does, look at the > driver source.

RE: Does Tomcat/Java get around the problem of 64K maximum client source ports?

2020-03-27 Thread John.E.Gregg
Chris, André, Eric, etc, A few random thoughts. First, this is really a MySQL driver thing, not a Tomcat thing. If you want to know why the driver does what it does, look at the driver source. There is actually a Socket constructor that allows you to specify the local port. I don't know

Re: Practical multipart handling

2020-03-27 Thread Mark Thomas
On 27/03/2020 15:52, Christopher Schultz wrote: > On 3/26/20 18:44, Konstantin Kolinko wrote: >> I think that those are available via the standard >> request.getParameter(name) API. > > That doesn't work. Mixing request.getParameter() and request.getParts > results in request.getParameter*

Re: valve execution order

2020-03-27 Thread Mark Thomas
On 23/03/2020 14:23, Jonathan Yom-Tov wrote: > What about valves which are added programmatically within the same engine? > Is it possible to control the order? Not directly. Valves added programmatically are added to the end of the Pipeline. There isn't an insertValve() method so you need to add

Re: Does Tomcat/Java get around the problem of 64K maximum client source ports?

2020-03-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Eric, On 3/26/20 13:58, Eric Robinson wrote: > Many people say the maximum number of client ports is 64K. > However, TCP connections only require unique sockets, which are > defined as... > > local_IP:local_port -> remote_ip:remote_port > >

Re: Practical multipart handling

2020-03-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Konstantin, On 3/26/20 18:44, Konstantin Kolinko wrote: > чт, 26 мар. 2020 г. в 18:03, Christopher Schultz > : >> >> All, >> >> I'm developing my first multipart handler since .. I dunno, >> maybe 2005? This is the first time I'll be using the

Re: Practical multipart handling

2020-03-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Michael, On 3/26/20 12:36, Michael Osipov wrote: > Am 2020-03-26 um 16:03 schrieb Christopher Schultz: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> >> All, >> >> I'm developing my first multipart handler since .. I dunno, >> maybe 2005?

Re: Strange side effect of "antiClickJackingOption" clause in "httpHeaderSecurity"

2020-03-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 3/26/20 12:54, James H. H. Lampert wrote: > On 3/24/20 2:25 PM, Christopher Schultz wrote: >> I don't understand exactly how X-Frame-Options (which is what >> the HttpHeaderSecurityFilter is configuring) is being used by >> your

Re: Does Tomcat/Java get around the problem of 64K maximum client source ports?

2020-03-27 Thread tomcat/perl
On 27.03.2020 14:27, André Warnier (tomcat/perl) wrote: On 26.03.2020 20:42, Eric Robinson wrote: -Original Message- From: Olaf Kock Sent: Thursday, March 26, 2020 2:06 PM To: users@tomcat.apache.org Subject: Re: Does Tomcat/Java get around the problem of 64K maximum client source

Re: Does Tomcat/Java get around the problem of 64K maximum client source ports?

2020-03-27 Thread tomcat/perl
On 26.03.2020 20:42, Eric Robinson wrote: -Original Message- From: Olaf Kock Sent: Thursday, March 26, 2020 2:06 PM To: users@tomcat.apache.org Subject: Re: Does Tomcat/Java get around the problem of 64K maximum client source ports? Hi Eric, On 26.03.20 18:58, Eric Robinson wrote: