Based on the "Events" tab in the properties dialog of the OCX, it only 
sees GET, GET Query, POST, and HEAD requests.

Your idea to rewrite the requests via a proxy server sounds like the 
best idea.  I've never tried this, so I can't offer any other help. 
(I've never even researched PUT or DELETE requests, so I have no idea 
how they're different from GET and POST requests.)

Liz


On 13 Oct 2016 07:35, Jim Moseley wrote:
> All,
>
> So I'm adding an interface to my app from an API that uses GET, POST,
> PUT, and DELETE requests.  I know the CWS OCX can handle the GETs &
> POSTs, but have no idea if it will even see the PUT & DELETE requests.
>
> Does anyone have a recommendation for handling these requests?
>
> Since we also use the ISAPI_Rewrite app to handle the reverse proxy, I
> might have to figure out how to have that redirect these as GETs &
> POSTs, like:
> DELETE 'mydata' becomes POST 'mydata_DELETE'
> PUT 'mydata' becomes POST 'mydata_PUT'
>
> I can then handle these.
>
> TIA,
> Jim Moseley