DSpace 7.6.3; 502 Bad Gateway Errors on three specific resources

[Carolyn Sullivan]

Hello,

So bizarrely, three resources that were created today are giving us 502 Bad Gateway Errors when we try to connect to them via the URL or the Handle.  However, if we try to connect to them through the DSpace interface via the collection they're in, we can navigate to the pages in question without any problem.  None of the other resources created today are having this issue.  Has anyone encountered this behaviour before?  Is it just going to take time for these materials to be indexed or something?  Is there something I should look for in the Handle Error logs or the tomcat logs?

Thanks,

Carolyn.

[محمود محمد‎]

---

I have bibliographic record files totaling 10,000 records, corresponding to 10,000 items in an Excel file, which I have successfully migrated into DSpace. Additionally, I have created authority records for 20 institutions within the "orgunit" entity group and linked them to the items as publishers. However, when the number of items linked to a single institution exceeds 1,000, a relation issue arises: the orgunit record for the institution does not accept being linked to more than 1,000 Publication items. What is causing this issue, and how can I resolve it?

--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/73de71a8-cc12-4b3d-a5f6-7215844465ffn%40googlegroups.com.

[Carolyn Sullivan]

Okay, so it was because the three records in question had >50 files attached to them and sign-posting was active, which made the header too large and triggered this error: https://github.com/DSpace/DSpace/issues/8943

[Carolyn Sullivan]

Follow-up question--the initial ticket says, 

'If using Apache with mod_proxy, the setting to change is responsefieldsize. It needs adding to the ProxyPass of the apache configuration, e.g.

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?'

Why would increasing the responsefieldsize for apache not be a very secure option?

On Monday, March 24, 2025 at 4:45:52 PM UTC-4 Carolyn Sullivan wrote: