fkooman

> Am I supposed to block access to 192.168.12.0/24 -except 192.168.12.1- by routing it through 10.1.2.1? As far as I know this is exactly what happens yes! See below example...

Not sure, maybe this could be a restriction on iOS?

I also want to make a https://dply.co/ script to deploy it in "one click" for testing purposes.

I'll look at this after 2.0 :)

Right. That makes sense. Back then it was either violate the OAuth specifcation or the remoteStorage specification. To be fair, the "authorize" page does show both the `client_id` and `redirect_uri`....

I just realised that's pretty much what you said :)

The current check is obviously broken and should be fixed. Comparing `Origin` seems to be the most sensible yes: `scheme :// host (:port)`

Untested as of right now. Any of you in the position to test this out?

I didn't test it for a long time now. In order to get this going again we really need to run the test suite against it to make sure all...

Sorry, I never got a notification for the redirect URL issue, only seeing it now... Also, I would not recommend running this with mod_php, but instead with php-fpm...