WADL file is hidden

Bug #548429 reported by Monty Taylor on 2010-03-25
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

The launchpad API WADL file is inextricably hidden behind OAuth, meaning one has to use the launchpad API to get at the description of the launchpad API. This makes it very difficult for people who are not using the python launchpadlib (like, someone working in Java) to get started. Heck. even just having a URL I can download it from through my web browser that's protected via LD SSO would be something - since at least then I wouldn't have to inject the extra requests for content-type wadl

But really - it's the description of your API. It should be VERY easy for me to integrate it into the app I'm working on. I spent the morning and chatted with two different people on IRC before I could get a copy.

Leonard Richardson (leonardr) wrote :

I have no objection to stopping Launchpad from guarding the service root resource.

Gary Poster (gary) wrote :

Agreed that this should happen. It should be a relatively easy change.

Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
milestone: none → 10.05

Can't the WADL file be present on the apidoc[1] page next to the each version?

[1] https://edge.launchpad.net/+apidoc/

Martin Pool (mbp) wrote :

@Manish, linking to it from the apidoc page could be good, but would be a separate bug. There is one complication that at the moment iiuc you can only get it by passing an Accept header which prefers wadl, and so a regular web browser can never download it. It would be nice to offer an alternate url.

The good news is that this should now work, without authentication. I think it was implicitly fixed as part of allowing anonymous api access:

  curl -v https://api.launchpad.net/devel/ -H "Accept: application/vd.sun.wadl+xml"

The bad news is right at the moment it's timing out.

Martin Pool (mbp) wrote :

OK, that command does work, but it is a bit slow and might time out.

Martin Pool (mbp) wrote :

bug 607961 is the timeout problem. If you retry you should get it ok.

bug 708994 is asking for a plain url, which could be put in the docs.

Martin Pool (mbp) wrote :

Aside from those issues, I think this is now fixed. Please reopen if I'm wrong.

Changed in launchpad:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers