[Seasar-user:12350] Re: websphere url rewriting

Koichi Kobayashi [E-MAIL ADDRESS DELETED]
2007年 12月 28日 (金) 19:00:05 JST


$B>.NS(B (koichik) $B$G$9!%(B

$B$b$C$H>pJs$rDs6!$7$F$/$@$5$$!%(B
$BNc$($P(B

$B!&$I$N$h$&$J2hLL$G!$$I$N$h$&$JA`:n$r$7$?$N$+$H$$$&@bL@!%(B
$B!&(BrequestDumpFilter $BEy$N%m%0!%(B
$B!&:F8=2DG=$J%5%s%W%k(B

$B$H$$$C$?>pJs$,$"$l$P2?$+J,$+$k$+$b$7$l$^$;$s!%(B


Date:    Fri, 28 Dec 2007 17:39:11 +0800
From:    <[E-MAIL ADDRESS DELETED]>
To:      [E-MAIL ADDRESS DELETED]
Subject: [Seasar-user:12349] Re: websphere url rewriting

> Thanks for your reply.
> 
> But my project did can't work under websphere.
> When i don't check on the url rewriting ,i can't login because of no session
> found and can't pass the filter.
> When i check on the url rewriting, it can automatically create jsessionid,
> but still works wrong
> Error 500: [ETDA0029]$B%7%M!"%R!&t'%?!&!"!&x'%C!&%M!"%*!"x&%K!"!"!"!m!"%1!#!W(B
> 
> Are you sure i don't need to do any special programming for this?
> Then how should i do the WAS session configuration?
> It seems useless only check on the url rewriting and cookie.
> 
> Or these's something wrong within teeda-sp2 (the teeda version i'm
> using)that caused my problem.
> 
> 2007/12/28, YASUO HIGA <[E-MAIL ADDRESS DELETED]>:
> 
> > Hi guys,
> > >
> > > Accroding to the ibm site , it is said that
> > > "
> > >
> > > An application that uses URL rewriting to track sessions must adhere to
> > > certain programming guidelines. The application developer needs to do
> > the
> > > following:
> > >
> > >    - Program servlets to encode URLs
> > >    - Supply a servlet or JavaServer Pages (JSP) file as an entry point
> > to
> > >    the application
> > >
> > >
> > > Must i "adhere to certain programming guidelines"?
> > > When i use tomcat as my application server, it runs well. The url ended
> > with
> > > jsessionid, and it is automatically added.
> > > So i wander if the "seasar + teeda" has already done it for
> > > us?(automatically rewrite url)
> > >
> > Teeda uses HttpServletResponse#encodeURL(), encodeRedirectURL().
> > So, if WebSphere implements Servlet API completely,
> > your application will works well.
> > You don't need to use response.encodeRedirectURL(...).
> > _______________________________________________
> > Seasar-user mailing list
> > [E-MAIL ADDRESS DELETED]
> > https://ml.seasar.org/mailman/listinfo/seasar-user
> >


-- 
<component name="koichik">
    <property name="fullName">"Koichi Kobayashi"</property>
    <property name="email">"[E-MAIL ADDRESS DELETED]"</property>
    <property name="blog">"http://d.hatena.ne.jp/koichik"</property>
</component>



Seasar-user メーリングリストの案内