Replies: 2 comments
|
Interesting idea. I wonder if this might be better implemented at the reverse-proxy level. What do you think? |
|
You are right. I already went into this direction (see below). ServerName flashpaper.domain.com ProxyPreserveHost On ProxyErrorOverride On RewriteEngine On SSLProxyVerify none RequestHeader set ClientProtocol HTTPS ProxyPass /fps/ http://linux-5dock.domain.com:8085/ ProxyPass / http://linux-5dock.domain.com:8085/ Enable authenticationEnable authenticationWith the parameter base_url, I defined to generate the links with /fps/... The Home button must reload / and not stay on /fps/. This is the reason behind the new parameter, so any user could send it to wherever they want... |
Uh oh!
There was an error while loading. Please reload this page.
I like the base_url parameter, but there should be a second parameter like base_url_home.
Reason:
If flashpaper is behind a reverse proxy, one might want to open the retrieval path (based on base_url) and protect the creation of new secrets. This all works, with one exception:
When a secret has been retrieved and the user clicks on Home, then he is able to create a secret without authentication i.e. the creation is no longer protected.
In order to have all options, the button should call the new parameter base_url_home.
All reactions