On 17.10.2012, at 08:46, Bart Visscher <[email protected]> wrote: > On Wed, Oct 17, 2012 at 06:52:50AM -0300, Frank Karlitschek wrote: >> Hi Bart, >> >> thanks a lot. >> Can you describe a bit how this works with non Apache Webservers like IIS >> and Nginx and with configurations where .htaccess is disabled or mod_rewire >> is not installed? > > It uses the same form as remote.php so no changes for htaccess is > needed. This just uses the pathinfo to define the route. Later we could > use rewriting of urls to get even nicer urls, but that is a later > change. > The only possible change to the configuration is when pathinfo is only > usable/configured for remote.php > > Bart
O.K. sounds good as long as it works on all webservers and all configuration that we want to support. :-) Please make sure that we always need an migration path and script for users if we change an url and people update to a new ownCloud version. Frnk >> >> Thanks. >> >> Frank >> >> >> On 17.10.2012, at 06:46, Bart Visscher <[email protected]> wrote: >> >>> Hello everyone, >>> >>> I am going to merge the routing branch this weekend. Everything should >>> keep working, let me know if it breaks something. >>> >>> With routing we can define our own url structure, and connect simple >>> functions to that. It also simplifies the creation of REST endpoints, >>> the conversion of PUT/GET/DELETE/etc to functions is all handled for >>> you. >>> >>> There are a couple of usage examples in the code, and also in the >>> ocs_api branch. After the merge i will convert some more. >>> >>> Bart >>> _______________________________________________ >>> Owncloud mailing list >>> [email protected] >>> https://mail.kde.org/mailman/listinfo/owncloud >> > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
