Hey Serhat,(first name right?) From what I understand you have a specific case. Today the squid project doesn't have an example on how to implement such a solution. I am willing to write an example for such a use case. If you are willing to give me some of the details privately I would be able to put up together an ICAP server as an example.
Eliezer ---- Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: elie...@ngtech.co.il -----Original Message----- From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf Of Amos Jeffries Sent: Wednesday, March 15, 2017 4:04 AM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Squid Authentication with HTTP REST API On 14/03/2017 8:15 p.m., Serhat Koroglu wrote: > Hello, > > Is there any possibilty implementing an authentication through a custom XML > Web Service or HTTP REST API? What should I check? > Squid supports the HTTP authentication framework (RFC 7235 <https://tools.ietf.org/html/rfc7235>). Squid is intentionally designed not to touch the message payloads. If the API uses custom headers then you can possibly do it with an external_acl_type helper that takes those headers and returns credentials to Squid. But, if the API uses message payloads you will likely need something like an ICAP service or eCAP module to do the payload processing. Amos _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
