I'm used to debugging REST-API calls via the browser. Now I'm only getting:

Requested content type is not available. Acceptable types: */*,
application/json 

I'm quite sure this used to work before. The error message itself is
from a commit in May (5744:d4de45cde106) but I'm sure I've debugged REST
in the browser after that date. So a recent change must have affected
that we can no longer view the JSON output from REST-API queries in the
browser.

Any idea?

This was too fast. Looks like I forgot the '?' in the query-URL. This
causes the REST framework to split the path at a '.' (dot) because one
of my query parameters contained a dot. And this in turn yields an
unsupported content-type via the "extension" (which happens to be the
rest of my query-string after the dot).

Sorry for the noise

Hi Ralf:

I just checked in a change that reports what type roundup thinks you
specified.  This should help with debugging I hope.

On Tue, Nov 26, 2019 at 02:57:28PM +0000, John Rouillard wrote:
> Hi Ralf:
> 
> I just checked in a change that reports what type roundup thinks you
> specified.  This should help with debugging I hope.

Thanks!

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: office@runtux.com