Thanks, I have been looking at the squid debug and can see that it is getting the multipart.
POST http://bbbbbb.com User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 Accept: application/json Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Referer: http://bbbbb.com Cache-Control: no-cache X-Requested-With: XMLHttpRequest Content-Type: multipart/form-data; boundary=---------------------------328901485836611227811186534509 Content-Length: 1245 Origin: http://bbbbb.com Cookie: cookie Host: bbbbbbb.com Via: ICAP/1.0 4dd -----------------------------328901485836611227811186534509 Content-Disposition: form-data; name="action" frm_submit_dropzone -----------------------------328901485836611227811186534509 Content-Disposition: form-data; name="field_id" 8 -----------------------------328901485836611227811186534509 Content-Disposition: form-data; name="form_id" 5 -----------------------------328901485836611227811186534509 Content-Disposition: form-data; name="nonce" e1aca92777 -----------------------------328901485836611227811186534509 Content-Disposition: form-data; name="file8"; filename="translate.zip" Content-Type: application/x-zip-compressed On Thu, Jul 23, 2020 at 11:16 AM Alex Rousskov < rouss...@measurement-factory.com> wrote: > On 7/23/20 9:22 AM, Ryan Le wrote: > > I have been trying to configure squid to decode and send multipart form > > data to another service. Is there an acl or build parameter needed for > > multipart form data support? > > No, there is no need to allow any specific Content-Type, including > multipart. Squid does not know anything about multipart/form-data. If a > multipart/form-data message is well-formed from HTTP point of view, then > Squid will process it as any other message, including passing it to > ICAP/eCAP (where configured). > > Cheers, > > Alex. >
_______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
