WebDAV Nav support for HTTP redirects

WebDAV Nav is able to correctly follow standard HTTP redirects (302 or 307) when initially creating a connection to a server.

This will enable server administrators to redirect users based on authentication details to different servers or folders.

###EXAMPLE

• The app is configured with a URL of http://example.org/, with no username or password entered
• The user attempts a connection to http://example.org/, the server responds requesting username and password
• A pop up appears on the users device requesting username and password, and then resubmits the request
• The server extracts the username from the request, and then sends a redirect response (HTTP 302 or 307) to the app with the users custom URL e.g. http://server2.example.org/username/
• The app then follows the redirect and connects to the new URL endpoint http://server2.example.org/username/
• To the user it appears that they have connected directly to their own folder

###SAMPLE SCRIPT As an example I’ve created a sample Python script that may be configured to provide this service.

WebDAVNav Redirector

This has been tested on a variety of platforms include Debian, Ubuntu and Raspberry Pi.

Once this server script is configured and running, you can direct all your WebDAV Nav clients to connect directly to this endpoint. It will then handle the redirect to your real servers

---