• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space

Chevereto behind a secured reverse proxy?

Pierre Lannoy

Pierre Lannoy

Chevereto Member
Hi Rodolfo and others!

I plan to use Chevereto for my next project, but I have some questions I can’t find answers… (sorry if I miss something in the forum, don’t hesitate to redirect me to the right conversations).

Here are the infra I plan to use :
- a web server behind a reverse proxy
- communication between web server and proxy are http
- communication between proxy and clients are https
- storage on S3

First question : are there any known incompatibilities to operate in this manner with Chevereto?
Second question : is there a simple way for Chevereto to produce https links (BBCode …)? (Reminder: the web server behind the proxy is http, not https)
Third question : do you have any specific advice or experience feedback about this way of doing?

Thanks in advance for all your answers
Pierre
 
Oh, and just a subsidiary question : is there a futur plan to Cheverto to use url shortners (like yourls)?

Thanks.
Pierre
 
1. I don't think that there will be issues at all. I've used a lot Apache+nginx as a reverse proxy and there is no issues so I can't imagine why there could be issues apart from a bad server setup. When doing reverse proxy you obviously need to forward and populate things like the client ip, referer, etc. In your case you will also need to inject "https=on" otherwise the links generated by Chevereto will be http not https.

2. Chevereto produce the internal links based on the detected protocol, server name, script path, etc. All that is detected using $_SERVER array, so in your server setup you must to inject the server name, path, etc.

3. I've done it tons of times with Apache+nginx and the only thing to worry about is that you need to map a lot of things but is not hard at all.

4. There are no plans for URL shortners. Way I see it, those things are not longer needed at this time.

Cheers.
 
You must log in or register to reply here.
Back
Top