<![CDATA[Omeka S on Cloudron as host for embedded exhibits - CORS]]>We are using Omeka S on Cloudron as an host for several online exhibitions.

Because something like https://omeka.<cloudron>.<tld>/s/<my-exhibit> is not a very nice and memorable URL, we would like to embed these exhibits in our primary website to get URLs like https://www.<museum>.<tld>/virtual-exhibits/<my-exhibit>.

We configured our nginx to handle these URLs and to get the content from Omeka, but we ran into a Cross-Origin Resource Sharing (CORS) issue. Searching the forum i found several entries regarding to CORS (e.g. Bug: CORS error), but there doesn't seem to be a consistent solution. In https://forum.cloudron.io/post/64706 @girish gives a quick workaround, but this is not consistent.

As this issue wasn't addressed in the specific forum and time goes by, i wonder if someone knows a solution for the scenario above. I'm pretty sure I am not the only one with this requirement.

]]>https://forum.cloudron.io/topic/10179/omeka-s-on-cloudron-as-host-for-embedded-exhibits-corsRSS for NodeFri, 17 Apr 2026 02:36:42 GMTWed, 11 Oct 2023 13:37:40 GMT60<![CDATA[Reply to Omeka S on Cloudron as host for embedded exhibits - CORS on Wed, 17 Jan 2024 13:40:55 GMT]]>@GeHo said in Omeka S on Cloudron as host for embedded exhibits - CORS:

Because the HTML itself delievered by Omeka loads scripts, images, css etc. from the domain of origin. This causes the CORS issues.

aren't all these covered by same origin policy exceptions ? https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy#cross-origin_network_access

]]>https://forum.cloudron.io/post/81267https://forum.cloudron.io/post/81267Wed, 17 Jan 2024 13:40:55 GMT<![CDATA[Reply to Omeka S on Cloudron as host for embedded exhibits - CORS on Wed, 17 Jan 2024 09:09:06 GMT]]>@girish

Why do you think this is a CORS issue?

Because the HTML itself delievered by Omeka loads scripts, images, css etc. from the domain of origin. This causes the CORS issues.

]]>https://forum.cloudron.io/post/81244https://forum.cloudron.io/post/81244Wed, 17 Jan 2024 09:09:06 GMT<![CDATA[Reply to Omeka S on Cloudron as host for embedded exhibits - CORS on Wed, 17 Jan 2024 09:07:36 GMT]]>@jeau Thanks for the suggestions, and sorry for replying this late. However: Happy New Year!

I don't think that using iFrames to embed an omeka exhibition is very convenient for the user, because he loses the ability to refer to or set a bookmark for a specific page.

]]>https://forum.cloudron.io/post/81243https://forum.cloudron.io/post/81243Wed, 17 Jan 2024 09:07:36 GMT<![CDATA[Reply to Omeka S on Cloudron as host for embedded exhibits - CORS on Sun, 15 Oct 2023 12:46:10 GMT]]>@GeHo I understand that your main site is not an Omeka installation and that you attempt to integrate each exhibit with an iframe as @nebulon suggests. Is this the case? The CORS issue could come from this approach.

I can suggest a solution for URLs. You can rename your Omeka site from https://omeka.<cloudron>.<tld> to https://virtual-exhibits.<museum>.<tld> or you can configure a web redirection from https://omeka.<cloudron>.<tld> to https://virtual-exhibits.<museum>.<tld>. Then configure the rewriting of the right-hand part of the URL by using Omeka-S-module-CleanUrl or by inserting rewriting rules in the .htaccess file at the root of your Omeka installation. You can modify the .htaccess file.

To integrate an Omeka exhibit into a site. I've tested it and it seems to work.

]]>https://forum.cloudron.io/post/75337https://forum.cloudron.io/post/75337Sun, 15 Oct 2023 12:46:10 GMT<![CDATA[Reply to Omeka S on Cloudron as host for embedded exhibits - CORS on Fri, 13 Oct 2023 15:25:30 GMT]]>Also how is the embedding happening on the main site? Are you adding an iframe or is there some other way with omeka-s to integrate?

]]>https://forum.cloudron.io/post/75257https://forum.cloudron.io/post/75257Fri, 13 Oct 2023 15:25:30 GMT<![CDATA[Reply to Omeka S on Cloudron as host for embedded exhibits - CORS on Fri, 13 Oct 2023 03:02:56 GMT]]>@GeHo If I understood your setup correctly, you configured nginx to translate www.<museum>.<tld> calls to your omeka.<cloudron>.<tld> ? If this is the case, then there shouldn't be any CORS issue. CORS issue is hit when the browser makes requests directly to omeka when you visit your main site and thus bypassing your nginx. Why do you think this is a CORS issue?

]]>https://forum.cloudron.io/post/75219https://forum.cloudron.io/post/75219Fri, 13 Oct 2023 03:02:56 GMT