[squid-users] Sorry if this has been asked but I can't find an answer anywhere ...

[Mike Yates]

There are no certificates to worry about, the api is expecting a token to
be included in the payload of the call.   So all squid needs to do is
accept the post from the internal server and pass that post to the external
servers url including the payload.

I hope that helps.

On Fri, Sep 24, 2021, 18:01 Alex Rousskov <rousskov at measurement-factory.com>
wrote:

> On 9/24/21 5:26 PM, Mike Yates wrote:
> > Ok so let's say the new server outside the dmz has a different name. I
> > need a squid server configuration that will just forward the api calls
> > to an external address.  So my internal servers will still point to Fred
> > ( which is now a squid server and has access to the outside world) and
> > will then forward the requests to the new server I have in the cloud.
> > Long story short I just need a pass through squid server.
>
> Will those internal servers trust the certificate you configure Squid
> with? In your example, you used "https://...". That usually means the
> internal servers are going to validate the server certificate. Can you
> make them trust the Squid certificate? Or does the API communication
> have to be signed by a fred.mydomain.com certificate that you do not
> control?
>
> The other pending question is whether those internal servers are
> configured to use a proxy (see the previous email on this thread) or
> always talk directly to (what they think is) the API service?
>
> Alex.
>
>
> > On Fri, Sep 24, 2021, 17:18 Alex Rousskov wrote:
> >
> >     On 9/24/21 5:09 PM, Mike Yates wrote:
> >     > I have a bunch of internal machines that do not have internet
> >     access and
> >     > any one of them is sending api post requests to another system on
> prem
> >     > and having no issues ….
> >     >
> >     >
> >     >
> >     > Example would be https://fred.mydomain.com/api/event
> >     <https://fred.mydomain.com/api/event>
> >     >
> >     >
> >     >
> >     > Now the problem becomes the fred server is being moved to the
> cloud so
> >     > the same https://fred.mydomain.com/api/event
> >     <https://fred.mydomain.com/api/event> is still valid but none of my
> >     > internal server can see fred and I don’t have access to the backend
> >     > servers to change their api calls.
> >
> >     AFAICT from your summary, "moved to cloud" here means that the API
> >     protocol stays the same, the API server domain name stays the same,
> the
> >     API URL path stays the same, but the IP address of that domain name
> will
> >     change. Please clarify if that conclusion is wrong.
> >
> >     If it is correct, then it is not clear how the change of an IP
> address
> >     would affect those making API requests using the domain name, and
> what
> >     role Squid is playing here.
> >
> >     Alex.
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20210925/500011ee/attachment.htm>