Hi, > Is this because the client wants the email url to come from the same the > domain ? If so the best option would be to use a nginx proxy this would > split the connections between 4d and S3 but the URLs sent to the end-user > would always be from the same domain. This way you can keep 4D wherever you > want and you can secure connections between the two. It doesn't make sense > to load the 4D web server delivering PDF files. Nginx can do that for you.
Nginx proxy is a solution of course. AWS CloudFront can also help you to have access to S3 objects with your domain in the URL (I think this is more efficient). HTH Bruno
signature.asc
Description: Message signed with OpenPGP using GPGMail
********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
