By default we assume you're versioning the RESTful protocol, hence the /v1
in front. If you're not interested in doing that you probably could switch
the servlet mapping to /tickets/ and the routing to /${ticketGrantingTicket}
I haven't tried it though.
-Scott
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia
On Thu, Aug 14, 2008 at 5:37 PM, dale77 <[EMAIL PROTECTED]> wrote:
>
> Scott,
>
> That /tickets/* wiki entry was my change! Not surprizing you didn't realize
> that you did it.
>
> Progress! However, with the /v1/* entry in web.xml my POST has to be:
>
> POST /cas/v1/tickets/
>
> This gives me a 400, bad creds which is a start!
>
> POST /cas/tickets/ gives me a 302 again.
>
> This is because "cas" is the web application root. How to we configure the
> system so that "/cas/tickets" will do the business instead?
>
> I was assuming that /tickets/* was required to route /cas/tickets/ to the
> restlet servlet... Does the routing in restlet-servlet.xml need to change
> to
> / and /{TGT}?
>
> Dale
>
>
> scott_battaglia wrote:
> >
> > I just realized I'm the reason that you chose "tickets" as the url
> > pattern.
> > My apologies. I didn't realize I put that into the wiki. I changed it
> to
> > something like /v1/*
> >
> > So you'll have something like POST /v1/tickets or GET
> > /v1/tickets/TGT-5435345435435353534
> >
> > -Scott
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/How-do-I-activate-the-new-RESTful-api--tp18885690p18990205.html
> Sent from the CAS Users mailing list archive at Nabble.com.
>
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas
>
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
