rest-call '/profiles' geeft een fout

[Michiel.Schok]

Is het een error 500 op deze niet bestaande call ?

[Frans]

Didn't you mean: /transcode/profile ?
That is an existing and valid call.

[Michiel.Schok]

No, I was aiming for the /transcode/profile call, but typed '/profiles' instead (to get a list of transcode profiles). That resulted in a '403' (forbidden).
Normally, non-existing calls return a nice xml-response.

Compare direct results on the pages
 http://app.acceptatie.vpcore.snkn.nl/profiles/
and
 http://app.acceptatie.vpcore.snkn.nl/nonexist/

But a '403' is better than a '500'. There must be an explanation for it... out there... somewhere...

[robert]

/profiles is a drupal directory and gives back 403 because you are not logged in as a drupal user to access the page.

Tested on 1.7.x and also returns 403 on REST interface, so this is always been like this.

Think we need to fix this it for REST interface to return 404 in XML when set on exclusive XML output like we have in 2.x now.

Ideas?

[Michiel.Schok]

Well,
I'm satisfied with the explanations.
We could as well close the issue.

[Frans]

Will move to MM 2.2

[Frans]

Still valid?

[Frans]

Still valid, but won't fix