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: > 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. > > > -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/0ec68f40-88cd-40ba-ab18-26ab5aea5e18n%40googlegroups.com.
