Ticket #1299 (closed defect: worksforme)

Opened 13 months ago

Last modified 7 months ago

Symlinks doesn't work

Reported by: heavyhenning@… Owned by: jan
Priority: high Milestone: 1.4.19
Component: core Version: 1.4.13
Severity: normal Keywords:
Cc: Blocked By:
Need User Feedback: no Blocking:

Description

For some reason Lighttpd 1.4.13 doesn't want to show symlinks in the directory listing, and I get a 403 every time I try to access the symlink..

I have done server.follow-symlink = "enable" but it still doesn't work

If this is already fixed in newer versions, would you be very kind to send me an email, so I can notify the maintainers of the package, to update it.. :)

Attachments

Change History

Changed 13 months ago by darix

check all involved paths and their permissions. also the permissions of the parent directories of your symlinked file.

Changed 13 months ago by jan

  • milestone changed from 1.5.0 to 1.4.17

Changed 12 months ago by wemolohtrab+lighttpd at gmail dotcom

i was having the same problem but had not explicitly set server.follow-symlink = "enable" -- this setting was absent in my (default, fedora core 6) lighttpd.conf file. the docs say that it's enabled by default so i didn't think this was the problem. but eventually i tried adding server.follow-symlink = "enable", restarted lighttpd, and all was fine.

Changed 7 months ago by stbuehler

  • status changed from new to closed
  • resolution set to worksforme
  • pending unset

I don't think it is possible that there is a difference between a config with a global server.follow-symlink = "enable" statement and a config without it, if you did not use it in any conditional.

So, the first bug seems to have been a permission problem (missing userfeedback), the second one is not a follow-symlink problem - it could be a general config problem of course; i hope there will be some (positive) changes/fixes for 1.4.19 - but there are enough tickets open for these ;-)

Add/Change #1299 (Symlinks doesn't work)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.