Litespeed blocks HTTP PATCH requests, Error 400

[foxyfred]

I'm trying to deploy a new REST API that we developed and it uses the "PATCH" HTTP verb/method to modify server-side resources.

Here's what Litespeed logs on an example PATCH request:

2013-01-24 13:31:17.864 [INFO] [199.47.220.172:37018-0] Status 400: Bad request method: PATCH /stores/66

It also shows the built-in "404 not found" error page.

Thing is, we need to support this method. It's even got RFC support: https://tools.ietf.org/html/rfc5789

How can I configure Litespeed to let that method pass?

[mistwang]

sure. we will add it to our 4.2.2 release.

[foxyfred]

Thanks for the quick response! Any idea on how soon we might expect a 4.2.2 release?

[NiteWave]

you can manually download 4.2.2 now, see if it's working as expected.
just change the version number in current 4.2.1 official download link.