tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Günter Kukies <guenter.kuk...@heuft.com>
Subject Re: HTTP Error 302
Date Tue, 25 Nov 2003 07:15:37 GMT
No, I can't use a forward(), because the FOP is interpreting a fop:image tag
and the FOP-Generator is requesting the image source. The things I can
change is the path to the ImageGenerator and the query piece of the
image-url.

Does the trick with including the session ID in my HTTP request work, when
the request comes from different clients????
Günter

----- Original Message -----
From: "Antonio Fiol Bonnín" <fiol.bonnin@terra.es>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Sent: Monday, November 24, 2003 9:01 PM
Subject: Re: HTTP Error 302


> If you are calling a servlet from another servlet using HTTP, that does
> not seem "the best approach". Can you use forward()?
>
> Otherwise, you can try to include the session ID in your HTTP request.
>
>
> Antonio Fiol
>
>
>
> Günter Kukies wrote:
>
> >Hi,
> >after investigating the Problem, we found that we generate a redirect to
> >login when
> >the session is invalid. We have a servlet, that generates Images. If the
> >client requests the Image servlet directly everything is fine. The
session
> >is valid and the user gets his image. But when the client want's to
generate
> >a PDF with FOP on the same webapplication where the Imigegeneratorservlet
> >is, we dont't get a valid session. The request to the Imagegenerator is
> >comming now from the webapplication and not from the client. So there is
no
> >session and we generate a redirect to login. I monitored the datatranfere
> >with tcpdump on the loopback device 127.0.0.1 and there I saw the HTTP
302.
> >
> >What is the best way to handle this kind of session problems.
> >
> >Thanks for answeres
> >
> >Günter
> >
> >
> >----- Original Message -----
> >From: "Christopher Schultz" <christopher.d.schultz@comcast.net>
> >To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
> >Sent: Friday, November 21, 2003 2:47 PM
> >Subject: Re: HTTP Error 302
> >
> >
> >
> >
> >>Günter,
> >>
> >>
> >>>what are the common reasons, that tomcat 4.1 is returning a HTTP 302
> >>>
> >>>
> >error page?
> >
> >
> >>Response code 302 is not an error: it is a redirect. Are you connecting
> >>to Tomcat via a browser or some other client?
> >>
> >>Your client should be "following" that redirect, which should be
> >>specified in the "Location" header of the response.
> >>
> >>For more information, check out the HTTP spec at:
> >>
> >>1.0 Spec: http://www.ietf.org/rfc/rfc1945.txt
> >>1.1 Spec: http://www.ietf.org/rfc/rfc2616.txt
> >>
> >>-chris
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >>
> >>
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message