[Sat Jul 01 14:52:38.800373 2023] [proxy_http:warn] [pid 4123617] (28)No space left on device: [client 172.22.88.64:0] AH10124: header size is over the limit allowed by ResponseFieldSize (8192 bytes). Bad response header: 'Link: <https://dev-www.repository.cam.ac.uk/bitstreams/cbaf36e9-[...] ; rel="item" ; type="audio/mpeg" , <https://dev-www.repository.'
[Sat Jul 01 14:52:38.800435 2023] [proxy_http:warn] [pid 4123617] [client 172.22.88.64:0] AH01106: bad HTTP/1.1 header returned by /items/f5eff2ac-3208-4e90-96ee-14cd68e8d1ac (GET)
I have tried increasing the apache setting as per guidance: https://httpd.apache.org/docs/2.2/mod/core.html#limitrequestfieldsize but the issue still persists.
I can also confirm that when disabling signposting, the issue disappears.
Anyone experiencing the same behaviour?
ProxyPass / http://localhost:4000/ responsefieldsize=12392
In case it helps others seeing the same issue. Increasing this to a very large number does not seem like a very secure option. Would it be possible for the signposting feature to include a configuration setting to limit the number of links added to the header?
Best,
Agustina