Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 494
    • Issues 494
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 32
    • Merge Requests 32
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #4761

Closed
Open
Opened Aug 12, 2017 by Erik Hepsø@erik

Webdav login is in a loop

When creating a new webdav folder the AuthName directory is set to "Restricted Area" as specified in issue #4699 (closed), and fixed in commit 10b48990.

This change unfortunately broke webdav access on my folders. Adding or creating a valid-user with htdigest creates the user with your newly created folder-name as the realm. But when you later on go to authenticate the server will not find any user that is allowed within the realm "Restricted Area", which is statically coded.

I had to change the code referred to in issue #4699 (closed) back to inserting $fn into the vhost configuration when adding a new webdav folder. This way at least it works. But of course it is fatal for the Apache service if someone tries to add Directory / as their shared folder.

Checking that the $fn variable is not empty or just / would be needed to prevent Apache from crashing at that point.

Assignee
Assign to
3.1.7
Milestone
3.1.7
Assign milestone
Time tracking
None
Due date
None
Reference: ispconfig/ispconfig3#4761