[Archivesspace_Users_Group] Error on creating new resource record: 413 request entity too large

[Chris Fitzpatrick]

Hi Angela,


This is an Nginx issue, which is what you're using as a proxy to sit in front of ASpace.


The likely fix is to up the client_max_body_size in your nginx config,


b,chris.


Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Angela Kroeger <akroeger at unomaha.edu>
Sent: Thursday, October 29, 2015 6:07 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Error on creating new resource record: 413 request entity too large


Often lately, when I'm creating a new resource record, I get an error message: "413 Request Entity Too Large nginx/1.7.12."



These are brief, collection-level records with no components, maybe half a dozen notes (individually none longer than a paragraph), two or three linked agents, three or four linked subjects, and maybe one instance. Nothing seems "too large" (or even slightly large) here, so I have no idea what specifically is triggering the error.



I can hit the browser's back button and try again, and the record will save on the second try, but several of the fields I had previously input will be gone, including any links to agent and subject records, instances, and classifications. My date subrecord, extents, and notes usually survive intact. When I try to add the missing information back in, I get the 413 error again unless I add only one piece of information at a time (that is, add the classification, save, add the instance, save, add one subject heading, save, add another subject, save, etc.).



This problem is relatively new. In the past (earlier releases of the software), I could input a complete record, even a much larger and more complex record, with no problem. Over the last few weeks, it's been happening with the majority of new resource records I've created.



Has anyone else experienced this?



I think we are still on 1.4.0, but I couldn't find anywhere in the system to confirm this.



Thank you!

--Angela



Angela Kroeger

akroeger at unomaha.edu<mailto:akroeger at unomaha.edu>

Archives and Special Collections Associate

Dr. C.C. and Mabel L. Criss Library

University of Nebraska at Omaha

(402) 554-4159


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151029/a55bded2/attachment.html>