The error is a 501 HTTP error being spit out by Cherokee. Unsure if it's the one actually creating the error though.
The issue results when I put pound (a load balancer) behind Cherokee and in front of our app server. We swapped pound with balance and the error went away. Arggh! Anyone on the list want to talk about your failover/scalability implementation? Interested in hearing how you are planning for any failure of Cherokee, your app server, etc. Wondering what the most sensible and easiest to manage without breaking functionality like pound did --- is? On Wed, Mar 2, 2011 at 8:28 PM, pub crawler <[email protected]> wrote: > Having an issue with a form post on one of sites. > > When form gets submitted I am getting this in the browser: > > This method may not be used. > > I've stripped everything down so just now Cherokee and our app server > and this persists. > > I am unsure what this error means and if it truly is coming from my > app server or Cherokee. > > Anyone have any insight on this one? > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
