Overview

When implementing CORS configuration for a Docker-based Omeka S as described in the following article, a server error occurred. This is a memo about that issue.

Dockerfile

The target is a Dockerfile like the following.

FLRERR#RR#AR&&&&C#CR&&&&&&VCRAUNUUUURU&&&&OOU&&&&&&OMOBNVNNPNNDGNPCPNLDMEHourrmYoYrlrlcfULaDaazllliuwPddwvwnmmvnmmnmnhiM[p2EppliiimngoonegzfkonE"hmeBttibbbazeecclrei-i/d---wdapanI--bpjfgitxkkostpvrv.gdivsRsnp:imAgg1nprepteeaiafahuarafvaanoNeeggeemerrdoh-rrtrtr-vacptd_tt--gea\n--ntq//aea-vvRarhaaFdd-tgsppO=twwcbpwavar/ecirR-ieedyiihhm4pwawcawrarw/w2hneOqnvvepcoppe.svwrweoswrwww-eewNqsvekn--k1:a//slevwwwwwfrrTt6seea./rwosu.ahwww-w/o=iEua-\xx-1/mwmmirtwwwd/hr"tNpldttsgweween/m/wahteSeDdle--iwk/kvsiwlhhttmgaavictwahaaw/thtamlrtnt-noh/-t-rawcmtm:l/oooeysnuosms/nv/olmlw/vurntfbm-lwdahn/lwvonui&\ai.e$wrtfvwoldn&lgck{wp/mifo-lu"Ntluoavv/ewlglildum]aearm-eahrw//uluamekrp-e/srrtmwdmemte/aatjo-s/mi/oaesea/mc-$gm$iwlshlt///utg(de{ow/stuacf-rienkvnw.immboivtavtpae}/holeanlayer-/r.htn//sferp<-owosztasfeisenqcimiimcoi.gwaq)teoplclli/wf.hkn/euendwk-i-a}\smsiav/-aycj-.setahemopsz\artxuune/icb/merpvgrpoawlcag=ensw/.rp/l-fewc1aduedi.h2dosagihm6ers/nto3p/evimd@disalgon/r/6m_cdvf0amlwai0iyuwwrllsdnw/e{.qelws}cl/woaw\\mmd/;>y-/h"swvtqi$mlt{lihv/-ecgfrodrsneifeoitngy}/p/deoa=mt/eaukbsaar-s/sei-.n$ic{nlviuedr\es/ion}.zip-Ovar/www/omeka-s-${version}.zip\

Cause and Solution

The following line needed to be added.

RUNa2enmodheaders

Summary

I hope this helps anyone experiencing the same issue.