Christian,
Thanks for clearing up the mystery.
We went back to the v2 api whose raw URLs look like:
/api/v2/yaml/blob/show/cm/ultrasound/revision?login=...token=...
As near as I can tell, the equivalent v3 url would be
/api/v3/repos/cm/ultrasound/git/blobs/revision?access_token=...
but the
Hi. I am trying to update a review request to add a target group and I got
it to work using curl, but if I try the same command using Java using
Spring RestTemplate or Apache Commons HttpClient, it doesn't work. I get a
200 response code but there is no update being done. Can someone tell me
Hi Joe,
Yeah, you'd have to set the content type. That's one of the reason we ended
up moving to the new model, so that we can more easily send the headers we
need and process the resulting data.
Glad it's working now!
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -
Been sick and behind on some emails. Catching up.
On Oct 4, 2012, at 14:33, Chris Clark chris.cl...@actian.com wrote:
The FF user who had problems has Firebug installed ready for the next time,
nothing has happened so far.
In a similar vein, I've Windows XP user with IE8 (the latest IE
We have an old Perl script we use to create reviews. It was written against
the old 1.5 API and I'm looking at porting it to the new 1.6 API.
Unfortunately, I can't get past the login step. In the old script we used
this uri:
api/json/account/login/
I've tried various alternative paths for
There's no specific login URL. The new API uses HTTP Basic
authentication for all requests.
-David
On Mon, Oct 8, 2012 at 4:47 PM, Steve seide.al...@gmail.com wrote:
We have an old Perl script we use to create reviews. It was written against
the old 1.5 API and I'm looking at porting it to
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 2762 by ben.como...@gmail.com: cannot edit People on review
request page, get a jquery error.
http://code.google.com/p/reviewboard/issues/detail?id=2762
* NOTE: Do not post confidential information in this bug report. *
*
