A plain
should suffice.
Giacomo Morri wrote (at 2024-04-24 12:03 +0200):
> Hi Holger, thanks for your reply.
>
> consider that the symlink is /MTF/Content -> /realt/path/, how can i set the
> Resource element for that path?
>
> Regards,
>
> Giacomo
>
>
>
> On 24/04/24 11:55, Holger Klawitter
Hi, i have a servlet for uploading files inside a path that contains a
symbolic link, the upload works fine with tomcat 7 but after upgrading
it to tomcat 9 the servlet give me a java.lang.NullPointerException at
java.io.File..
I tried setting the allowLinking param to true for the context in
Hi Holger, thanks for your reply.
consider that the symlink is /MTF/Content -> /realt/path/, how can i set
the Resource element for that path?
Regards,
Giacomo
On 24/04/24 11:55, Holger Klawitter wrote:
Hi,
allowLinking goes into a Resource Element inside Context,
not into Context
Hi Chris,
Sorry I understood wrongly here with regards to my environment, Let me
start from the beginning. I donot want to use redirect at all. I simply
wanted to force apache tomcat to use both localhost and dns name of the
localhost via url.
I have DNS resollution as below.
server.lbg.com -->
Thanks. it works fine.
G
On 24/04/24 12:27, Holger Klawitter wrote:
A plain
should suffice.
Giacomo Morri wrote (at 2024-04-24 12:03 +0200):
Hi Holger, thanks for your reply.
consider that the symlink is /MTF/Content -> /realt/path/, how can i set the
Resource element for that path?
Lavanya,
On 4/24/24 07:37, lavanya tech wrote:
Sorry I understood wrongly here with regards to my environment, Let me
start from the beginning. I donot want to use redirect at all. I simply
wanted to force apache tomcat to use both localhost and dns name of the
localhost via url.
When you say
Hi,
allowLinking goes into a Resource Element inside Context,
not into Context itself. This changed in Tomcat 8.0 IIRC.
Giacomo Morri wrote (at 2024-04-24 11:42 +0200):
> Hi, i have a servlet for uploading files inside a path that contains a
> symbolic link, the upload works fine with tomcat 7
Op do 18 apr 2024 om 17:42 schreef Mark Thomas :
> On 18/04/2024 15:18, Stefan Ansing wrote:
> > Hi Rémy, Mark,
> >
> >
> >
> > I just want to make sure that we’re understanding each other. I can see
> > that the connection needs to be closed in certain conditions to prevent
> > request smuggling
> Assuming it's easy for Tomcat to differentiate between errors generated
My PR was based on the assumption that it is easy, since Tomcat always
invokes this method[1] if it's a badRequest.
[1]
Hi Chris,
Thanks for the reply.
Local host means the machine i am logged in to server.lbg.com
You are right, example.lbg.com is CNAME record.
I dont have any SAN configured for the certificate. The certificate is
requested for only server.lbg.com
So if i just request new certificate with SAN
Stefan,
On 4/24/24 13:58, Stefan Ansing wrote:
Op do 18 apr 2024 om 17:42 schreef Mark Thomas :
On 18/04/2024 15:18, Stefan Ansing wrote:
Hi Rémy, Mark,
I just want to make sure that we’re understanding each other. I can see
that the connection needs to be closed in certain conditions to
Lavanya,
On 4/24/24 15:39, lavanya tech wrote:
Local host means the machine i am logged in to server.lbg.com
You are right, example.lbg.com is CNAME record.
Okay, thanks for clearing that up.
I dont have any SAN configured for the certificate. The certificate is
requested for only
12 matches
Mail list logo
