RE: Disabling ContextId's?

Jacob Kjome <[email protected]>
Newsgroups gmane.comp.java.enhydra.barracuda.general
Message-ID <[email protected]>
Have you taken this idea any further?  I think it could do the job and it 
would also hide things such as the $csjs stuff as well.

Jake

At 10:57 AM 7/15/2003 -0600, you wrote:
>Hmmm...I like this idea a lot; I hadn't considered it before, but I think it
>has definite merit. It may take a bit more work, but sounds like a better
>"long term" solution. Anyone else have comments about this?
>
>Christian
>----------------------------------------------
>Christian Cryder
>Internet Architect, ATMReports.com
>Project Chair, BarracudaMVC - http://barracudamvc.org
>----------------------------------------------
>"Coffee? I could quit anytime, just not today"
>
>
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]]On Behalf Of Jacob Kjome
> > Sent: Tuesday, July 15, 2003 9:54 AM
> > To: [email protected]
> > Subject: RE: [Barracuda] Disabling ContextId's?
> >
> >
> >
> > Couldn't we add a custom header and read from that instead of
> > appending the
> > context id to the URL?  Would that fix the issue?  Seems like we could do
> > this for the $csjs variable as well.  Then we'd never force Barracuda
> > specifics on people (overtly).  Proprietary headers would be ignored by
> > those who don't care about them.  What do you think?
> >
> > Jake
> >
> > At 09:35 AM 7/15/2003 -0600, you wrote:
> > >Hmmm....I don't think there's a way of doing that at this
> > point...of course,
> > >it could be easily modified, but could you upgrade to the latest
> > version if
> > >we do that?
> > >
> > >Basically, the reason the context id is getting appended is so
> > that when the
> > >request comes back you "maintain" any local context info you had prior to
> > >issuing the redirect...what we probably _ought_ to do is only append the
> > >context id when we can determine that the URL being fired will
> > be handled by
> > >Barracuda (ie. contains a .event or .form or something like that).
> > >
> > >In your case, because something else willb e handling it, the context id
> > >really shouldn't be appended...
> > >
> > >Christian
> > >----------------------------------------------
> > >Christian Cryder
> > >Internet Architect, ATMReports.com
> > >Project Chair, BarracudaMVC - http://barracudamvc.org
> > >----------------------------------------------
> > >"Coffee? I could quit anytime, just not today"
> > >
> > >
> > > > -----Original Message-----
> > > > From: [email protected]
> > > > [mailto:[email protected]]On Behalf Of Kirk Daries
> > > > Sent: Tuesday, July 15, 2003 9:19 AM
> > > > To: [email protected]
> > > > Subject: [Barracuda] Disabling ContextId's?
> > > >
> > > >
> > > > Hi Guys,
> > > >
> > > > I need to disable the contextId when throwing a ClientSide redirect.
> > > >
> > > > E.g.
> > > >
> > > > http://eworks.wcape.gov.za/testeworks2-reports/rwcgi60?testeworks2
> > > > -pdf+repor
> > > > t=exp_r_1084+p_adviceid=32289&$ctxid=_1058281548048
> > > >
> > > >
> > > > Need to make a call to Oracle Reports.. and it moans and groans
> > > > about extra
> > > > parameters in the url.
> > > > The above url it complains about because of the extra context id
> > > > parameter...
> > > > Is there any way to disable context id across the application or
> > > > just for a
> > > > single redirect?
> > > >
> > > > Thanx
> > > > KD
> > > >
> > > > _______________________________________________
> > > > Barracuda mailing list
> > > > [email protected]
> > > > http://barracudamvc.org/lists/listinfo/barracuda
> > >
> > >_______________________________________________
> > >Barracuda mailing list
> > >[email protected]
> > >http://barracudamvc.org/lists/listinfo/barracuda
> >
> > _______________________________________________
> > Barracuda mailing list
> > [email protected]
> > http://barracudamvc.org/lists/listinfo/barracuda
>
>_______________________________________________
>Barracuda mailing list
>[email protected]
>http://barracudamvc.org/lists/listinfo/barracuda
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.