I am, and I dont think it's the filter. Beyond that, the whole thing is broken now and I don't know why, so let's just forget I said anything ________________________________________________
Kevin Huntly Email: kmhun...@gmail.com Cell: 716/424-3311 ________________________________________________ -----BEGIN GEEK CODE BLOCK----- Version: 1.0 GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E--- W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+) PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++ G++ e(+) h--- r+++ y+++* ------END GEEK CODE BLOCK------ On Thu, Apr 13, 2023 at 2:14 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > Kevin, > > On 4/12/23 19:35, Kevin Huntly wrote: > > I'm seeing some odd behavior - my servlet filter is redirecting with port > > 10943 attached to the redirect > > Are you the author of the filter? If so, can you post the code that is > determining what URL to use for the redirect? > > > - that port is the port httpd is listening > > on, but there's a redirect under the covers for TCP 443 to TCP 10943. > > Please be careful with terminology. I suspect in your above sentence > "redirect" doesn't mean "HTTP redirect". What /does/ it mean? > > > I'm not sure how it's doing this, since there are no calls to getPort > > or anything like that. If you need to see the code let me know and > > I'll shoot over the github repo > Also post your <Connector> configuration. > > -chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
