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.
On Fri, Sep 24, 2021, 17:18 Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> 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
>
>
>
> Now the problem becomes the fred server is being moved to the cloud so
> the same 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.
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
