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
For several endpoints for the logical submission, if you specify the instance ID of a submission edit, Backend will redirect to the corresponding submission version endpoint:
I think the issue is that if the instance ID is encoded in originalUrl, then originalUrl does not contain `/submissions/${params.instanceId}`, because params.instanceId is not encoded. In that case, it doesn't complete the replacement, so it ends up redirecting the user to the same originalUrl.
The text was updated successfully, but these errors were encountered:
For several endpoints for the logical submission, if you specify the instance ID of a submission edit, Backend will redirect to the corresponding submission version endpoint:
central-backend/lib/resources/submissions.js
Lines 360 to 375 in e9dba19
For example, on the QA server, there's a submission edit whose instance ID is
uuid:adcaefa3-91d7-4770-a49a-1f5607d0f2f3
. The instance ID of the root submission version isuuid:4b2b3e15-5675-4baf-9111-1a548cf312cd
. When I request https://test.getodk.cloud/v1/projects/414/forms/children_registration/submissions/uuid:adcaefa3-91d7-4770-a49a-1f5607d0f2f3, the redirect happens as expected. However, if the:
in the instance ID is encoded, the redirect doesn't happen: https://test.getodk.cloud/v1/projects/414/forms/children_registration/submissions/uuid%3Aadcaefa3-91d7-4770-a49a-1f5607d0f2f3. Instead, I get an ERR_TOO_MANY_REDIRECTS.I think the issue is that if the instance ID is encoded in
originalUrl
, thenoriginalUrl
does not contain`/submissions/${params.instanceId}`
, becauseparams.instanceId
is not encoded. In that case, it doesn't complete the replacement, so it ends up redirecting the user to the sameoriginalUrl
.The text was updated successfully, but these errors were encountered: