I would recommend comparing capabilities based on your access control requirements. For instance with squid, you can easily limit a POST to something like
https://s3.amazonaws.com but deny a POST to
https://s3.amazonaws.com/* ; some firewalls cannot get that granular without complexity of the rules. Why this particular example is important, is because it allows one to create an S-3 bucket but not put anything in
it; this way you can limit to which S-3 buckets one is authorized to access and how (i.e. GET vs POST). While this may not be relevant to your company's requirements, think of what are your company's requirements and make sure the solution meets all those
requirements. Joe From:
squid-users <squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx> on behalf of Antony Stone <Antony.Stone@xxxxxxxxxxxxxxxxxxxx> NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. |
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users