Fedora 6 Transactions

14 views
Skip to first unread message

Kilian Amrhein

unread,
Aug 3, 2021, 8:13:38 AM8/3/21
to Fedora Tech
Hi all,

we have set up Fedora 6 in a Docker-Container (fcrepo/fcrepo:6.0.0) behind an Apache Proxy.

However, we ran into issues modifying resources in a transaction.

When I put the entire Transaction-URL as Atomic-ID in the header as documented here [1] and here [2] (like so: Atomic-ID: http://localhost:8080/rest/fcr:tx/fd4f48c4-7c47-46ee-8907-af6411ae4215), I get: 409 - Invalid transaction id

It works, however, when I just put the GUID in (like so: Atomic-ID: bf7e7b55-fcba-459d-9299-3b23b0c324f6).


Cheers, Kilian


Benjamin Pennell

unread,
Aug 3, 2021, 11:11:45 AM8/3/21
to Fedora Tech
Hi Kilian,

The Atomic-ID header should work with either the full URI form of the transaction ID or just the UUID portion. We will need to update the documentation to indicate that the UUID is also acceptable.

I was not able to reproduce the issue you encountered, in testing I was able to provide the full URI form of the transaction ID as the Atomic-ID header. I tested using the fcrepo:6.0.0 docker container and the jetty console distribution. It may be that the Apache proxy you mentioned is affecting things, possibly by modifying the base URI in the header or some other arrangement. If fedora received a different base URI in the header then what is configured to be running on it would not be able to recognize the the Atomic-ID.

Kilian Amrhein

unread,
Aug 4, 2021, 6:50:19 AM8/4/21
to Fedora Tech
Thanks Ben for looking into it!
And yes, although I also tested other base-uris for the ID and switched all extra options in the proxy-config off, it might well be that there is/was something still different from what it should be. But it's good to know that using only the UUID is also acceptable and intended to stay in.

Reply all
Reply to author
Forward
0 new messages