Amit,
On 4/4/24 22:21, Amit Pande wrote:
I am in the process of migrating from Tomcat 9 (9.0.87) to Tomcat 10.1
(10.1.20).
https://tomcat.apache.org/migration-10.1.html Using the migration tool, I have
migrated the applications (which use Spring libraries 5.x).
While testing the migrated
Hello,
I am in the process of migrating from Tomcat 9 (9.0.87) to Tomcat 10.1
(10.1.20).
https://tomcat.apache.org/migration-10.1.html Using the migration tool, I have
migrated the applications (which use Spring libraries 5.x).
While testing the migrated apps( which use web socket), ran into:
Eric,
On 4/4/24 13:43, Eric Fetzer wrote:
Hi All,
When I originally set up my tomcat instance, I added the following to allow
manager access under /opt/tomcat/webapps/manager/META-INF/context.xml:
That worked wonderfully. Now I'm trying to add another IP range by
changing it to:
This is
LOL, I'm decent at regex Robert. I got the \d+ from what ships in the
context.xml:
127\.\d+\.\d+\.\d+
It looks like an attempt at saying localhost can get in as long as the
localhost IP starts with 127. I assumed it wasn't actually regex but some
"tomcat language"... Thanks for the education!
Sorry folks (Robert), but upon further testing, it looks like port 8080
isn't open on these IP's. I was mistaking the attempt to connect from my
curl command with a response. I withdrawal my question for now. I'll
reply to this thread if it doesn't work once the hole in the firewall is
carved
You need to read up on "regular expressions" (or "regex").
In a regular expression, a lowercase "d" is a single decimal digit. A "+"
means one or more of them. A period means ANY character (which is why you
have to escape it when you mean "period"). A backward slash means to treat
the character
Thanks for the quick response Robert! So I tried escaping the periods and
putting the \d+ for the * but it didn't work. Is the \d+ incorrect in
substitution for *?
On Thu, Apr 4, 2024 at 11:53 AM Robert Egan wrote:
> It looks like you need to escape your periods, like you did for 127\.
>
It looks like you need to escape your periods, like you did for 127\. etc...
1\.3\.5
Robert Egan
On Thu, Apr 4, 2024 at 1:44 PM Eric Fetzer wrote:
> Hi All,
>
> When I originally set up my tomcat instance, I added the following to allow
> manager access under
Hi All,
When I originally set up my tomcat instance, I added the following to allow
manager access under /opt/tomcat/webapps/manager/META-INF/context.xml:
That worked wonderfully. Now I'm trying to add another IP range by
changing it to:
This is not working. I tried to use 2\.4\.6\.\d+ as
Java is 1.8.0_391
On Thu, Apr 4, 2024 at 1:35 PM Timothy Resh wrote:
> I got the Object ID and version straight out of the Certificate using
> Keystore Explorer. I'm not sure why there is a difference.
>
> The "\" is because I manually deleted the beginning part of the path.
> It's correct in
I got the Object ID and version straight out of the Certificate using
Keystore Explorer. I'm not sure why there is a difference.
The "\" is because I manually deleted the beginning part of the path. It's
correct in the actual file.
Java is 1.8.
On Wed, Apr 3, 2024 at 6:11 PM Konstantin
As Suggested by @Tim i used precompiled jsp feature and now i am not
getting 500 error even i deleted the */tmp/tomcat** directory
@Bean
>
> public ServletContextInitializer preCompileJspsAtStartup() {
>
> return servletContext -> {
>
> Set jspPaths =
12 matches
Mail list logo
