This is excellent. Thanks for the support!
> On Sep 22, 2018, at 4:05 PM, Daniel Klco <daniel.k...@gmail.com> wrote: > > For the reference CMS app I put together a vagrant script with Apache httpd > proxying and caching content from Apache Sling using mod_proxy and > mod_cache. You can find it here: > > https://github.com/apache/sling-org-apache-sling-app-cms/tree/master/vagrant > > On Sat, Sep 22, 2018, 3:51 PM Eric Norman <eric.d.nor...@gmail.com> wrote: > >> Are you using sling standalone which has an embedded jetty servlet >> container inside it? If so, then think the general approach for putting a >> httpd server in front of a jetty based server would be to use mod_proxy as >> a reverse proxy. You should be able to do a web search for "jetty >> mod_proxy" to see some examples of how that configuration would look in >> httpd. >> >> However, I suspect there may be some limitations (or additional >> configuration) if you are intend to use some newer technologies like http/2 >> or websocket with another web server sitting between the client and >> sling/jetty. >> >> Regards, >> -Eric >> >> On Fri, Sep 21, 2018 at 8:58 PM Cris Rockwell <chrisisintheho...@gmail.com >>> >> wrote: >> >>> Hello >>> Sling as an application server should work well behind an httpd >> web-server >>> acting as a firewall, proxy and cache layer. Given Sling and Httpd are >> both >>> Apache projects for the web, it seems they are pieces in the same stack. >>> But I'm having trouble finding documentation other than Adobe's >>> mod_dispatcher (which is not OSS afaik). Can anyone recommend resources >> or >>> advice for configuring httpd to work with Sling? >>> Thanks! >>> >>
