Re: URL-encoding and "#"

Well that explains a lot. Similar issue for me. With url encoding, tomcat is dropping back slash and the plus symbol. On Oct 13, 2017 3:01 AM, "Mark Thomas" wrote: > On 13/10/2017 07:38, Peter Kreuser wrote: > > Chris, > > > > > > > > > > Peter Kreuser > >> Am 13.10.2017 um

Re: URL-encoding and "#"

Am 13.10.2017 um 12:48 schrieb Alex O'Ree: > Well that explains a lot. Similar issue for me. With url encoding, tomcat > is dropping back slash and the plus symbol. While I think it is perfectly eligible to strive for a most perfect alignement with standards and specs, I think Tomcat should

Re: Enforcing server preference for cipher suites

Hi Chris, thanks for sharing your opinion. Just my last comment here to close this thread. BSAFE is anyways EOL now (or will be soon). We are already working on a replacement. Currently we are using the latest and greatest version of BSAFE with extended support. Once again, thank you all for the

Re: URL-encoding and "#"

On 13/10/2017 17:09, James H. H. Lampert wrote: > Thanks to all of you who responded. > > I found a web page that explains it in ways that I can wrap my > 55-year-old brain around, and has an easy-to-read reference chart. > > https://perishablepress.com/stop-using-unsafe-characters-in-urls/ > >

Re: URL-encoding and "#"

Thanks to all of you who responded. I found a web page that explains it in ways that I can wrap my 55-year-old brain around, and has an easy-to-read reference chart. https://perishablepress.com/stop-using-unsafe-characters-in-urls/ Question: the problem first showed up on a web service that

Re: URL-encoding and "#"

On 13.10.2017 18:17, Mark Thomas wrote: On 13/10/2017 17:09, James H. H. Lampert wrote: Thanks to all of you who responded. I found a web page that explains it in ways that I can wrap my 55-year-old brain around, and has an easy-to-read reference chart.

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

On Thu, Oct 12, 2017 at 11:16 PM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Chris, > > On 10/11/17 5:21 PM, Chris Cheshire wrote: >> Working on a migration from 7 to 8.5, and in it I am now using the >> tomcat dbcp, instead

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

As a further test I just took out my explicit rollback in my DAOFactory close() method, and swapped back to commons dbcp. Added an update that wasn't explicitly committed, and it correctly did not get committed when the connection was closed. Swapped back to tomcat dbcp and repeated, it got

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris, Sorry, I had the autocommit true/false values mixed up in my mind. When you say you have "autocommit disabled in mysql config" what do you mean? On 10/13/17 10:17 AM, Chris Cheshire wrote: > > > As a further test I just took out my

Re: About Tomcat7.0.54 upgrade to Tomcat9.0.1

On 13/10/2017 05:32, wrote: > On 10/12/17 12:47 PM, wrote: >> After upgrading Tomcat to 9.0.1, the local webapp can't right >> work. But in tomcat 7.0.54 is good. > > Did you copy your Tomcat 7.0.x configuration file into your Tomcat > 9.0.x conf/ directory or did you start fresh? > >

Re: URL-encoding and "#"

Am 13.10.2017 um 09:01 schrieb Mark Thomas: > From memory, # isn't one of the allowed exceptions. > > The full list of invalid characters in the request line that Tomcat > started to check for is: > ' ', '\"', '#', '<', '>', '\\', '^', '`', '{', '|', '}' > > The allowed exceptions are (currently)

Re: URL-encoding and "#"

Chris, Peter Kreuser > Am 13.10.2017 um 04:29 schrieb Christopher Schultz > : > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > James, > >> On 10/12/17 8:44 PM, James H. H. Lampert wrote: >> Question: >> >> The application we're developing has a suite

Re: URL-encoding and "#"

On 13/10/2017 07:38, Peter Kreuser wrote: > Chris, > > > > > Peter Kreuser >> Am 13.10.2017 um 04:29 schrieb Christopher Schultz >> : >> > James, > On 10/12/17 8:44 PM, James H. H. Lampert wrote: Question: The application we're developing has

Re: URL-encoding and "#"

On 10/13/2017 10:42 AM, André Warnier (tomcat) wrote: Mmm. You are being a bit casuistic here. (Granted, not that I wasn't.) In the real world, I would expect that 99% of what is ever POSTed, /is/ form data. Not you ? 10 years ago I would have agreed, but with REST services there are many

Re: URL-encoding and "#"

On 13/10/17 18:42, André Warnier (tomcat) wrote: > On 13.10.2017 19:29, Mark Thomas wrote: >> On 13/10/2017 18:15, André Warnier (tomcat) wrote: >>> On 13.10.2017 18:17, Mark Thomas wrote: On 13/10/2017 17:09, James H. H. Lampert wrote: > Thanks to all of you who responded. > > I

Re: URL-encoding and "#"

On 10/13/17, 10:50 AM, Igal @ Lucee.org wrote: On 10/13/2017 10:42 AM, André Warnier (tomcat) wrote: Mmm. You are being a bit casuistic here. (Granted, not that I wasn't.) In the real world, I would expect that 99% of what is ever POSTed, /is/ form data. Not you ? 10 years ago I would have

Re: URL-encoding and "#"

On 13/10/2017 18:15, André Warnier (tomcat) wrote: > On 13.10.2017 18:17, Mark Thomas wrote: >> On 13/10/2017 17:09, James H. H. Lampert wrote: >>> Thanks to all of you who responded. >>> >>> I found a web page that explains it in ways that I can wrap my >>> 55-year-old brain around, and has an

Re: URL-encoding and "#"

On 13.10.2017 19:29, Mark Thomas wrote: On 13/10/2017 18:15, André Warnier (tomcat) wrote: On 13.10.2017 18:17, Mark Thomas wrote: On 13/10/2017 17:09, James H. H. Lampert wrote: Thanks to all of you who responded. I found a web page that explains it in ways that I can wrap my 55-year-old

Re: AJP connection pool issue bug?

I missed some of these messages before.. I apologize. Can I send these to you privately. On Wed, Oct 4, 2017 at 4:01 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > TCD, > > On 10/4/17 3:45 PM, TurboChargedDad . wrote: > >