You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The RESTAPI, when called on a backend with a ++api++ (like for instance in https://6.demo.plone.org/++api++/) returns a wrong @id (i.e. without the ++api++ path).
Is this the intended behaviour?
To reproduce it
On https://6-classic.demo.plone.org the behaviour is as expected
But when calling the RESTAPI on a "backend" via the ++api++ path (e.g. https://6.demo.plone.org/++api++/). The returned @id points to a url without ++api++ in the path.
The returned @id is at https://6.demo.plone.org which is not the same as the requesting url https://6.demo.plone.org/++api++ (note the missing ++api++ path).
Calls based on the returned wrong @id will fail, e.g. the following
# the following fails because wrong @id
curl \
-i -X DELETE "${TYPE_AT_ID}" \
-H "Accept: application/json" \
--user ${USER}<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"><title>Error</title></head><body><pre>Cannot DELETE /@controlpanels/dexterity-types/mytype</pre></body></html>
Here is for instance necessary to first get the type id:
The RESTAPI, when called on a backend with a ++api++ (like for instance in
https://6.demo.plone.org/++api++/
) returns a wrong@id
(i.e. without the++api++
path).Is this the intended behaviour?
To reproduce it
On
https://6-classic.demo.plone.org
the behaviour is as expectedWith the returned
@id
one could e.g. delete the created type:But when calling the
RESTAPI
on a "backend" via the++api++
path (e.g.https://6.demo.plone.org/++api++/
). The returned@id
points to a url without++api++
in the path.The returned
@id
is athttps://6.demo.plone.org
which is not the same as the requesting urlhttps://6.demo.plone.org/++api++
(note the missing++api++
path).Calls based on the returned wrong
@id
will fail, e.g. the followingHere is for instance necessary to first get the type id:
The text was updated successfully, but these errors were encountered: