Hi folks,
I was just reading the specs on MailChimp's new API version 3.0, and discovered that it will be mandatory next year as version 2.0 is being turned off. Along with the usual GETs, PUTs, POSTS, and DELETEs, version 3.0 also requires the PATCH method for some requests. I didn't even know this existed, but I found some specs on-line(https://tools.ietf.org/html/rfc5789); apparently it's not new.
Is there any way to make this type of request with MvCALL?
----- Follow-up: ----- I just did some reading of MailChimp's docs, and I found this:
I suppose that will handle it for MailChimp. But in case a server doesn't support tunneling, is there another way? ----- -----
Thanks --
I was just reading the specs on MailChimp's new API version 3.0, and discovered that it will be mandatory next year as version 2.0 is being turned off. Along with the usual GETs, PUTs, POSTS, and DELETEs, version 3.0 also requires the PATCH method for some requests. I didn't even know this existed, but I found some specs on-line(https://tools.ietf.org/html/rfc5789); apparently it's not new.
Is there any way to make this type of request with MvCALL?
----- Follow-up: ----- I just did some reading of MailChimp's docs, and I found this:
Note
If your ISP doesn’t permit HTTP operations other than GET or POST, use HTTP Method tunneling: make your call with POST, but include the method you intend to use in an X-HTTP-Method-Override header.
If your ISP doesn’t permit HTTP operations other than GET or POST, use HTTP Method tunneling: make your call with POST, but include the method you intend to use in an X-HTTP-Method-Override header.
Thanks --
Comment