NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Apache, The Wall, and My Head More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

To slash... or not to slash... (Score:1)

by phillup (4419)

That is the question.

If I understand correctly...

You have a script alias of /music/

That means the URL must be /music/

If your script alias is /music

Then the URL can be /music

(I'm not totally positive... but, I think you have to list both to cover both cases)
- Re:To slash... or not to slash... (Score:1)
  
  by rob_au (1845)
  
  You're spot on with this - The problem does reside with the directory alias. The better definition of the directory alias would be:
  ScriptAlias /music /correct/path/to/dir
  
  Note the lack of trailing slashes in both the alias definition and the directory path - This will provide the correct functionality irrelevant of whether the web URL is invoked with the full path to index.pl or merely to the parent directory.
  - Re:To slash... or not to slash... (Score:1)
    
    by shockme (2685)
    
    I wish this was the answer. I really do, but the results are the same.
    
    --
    If things get any worse, I'll have to ask you to stop helping me.
- Re:To slash... or not to slash... (Score:1)
  
  by phillup (4419)
  
  Sorry, I got mixed up there a bit.
  
  Here is what my manual says about DirectoryIndex:
  
  ---
  
  The DirectoryIndex directive sets the list of resources to look for, when the client requests an index of the directory by specifying a / at the end of the a directory name.
  - Re:To slash... or not to slash... (Score:1)
    
    by shockme (2685)
    
    With a slash, without a slash, it's all the same. It keeps complaining that I'm attempting to execute a directory.
    Grr....
    
    --
    If things get any worse, I'll have to ask you to stop helping me.
Did you manage to fix this? (Score:1)

by tarquin (5005)

I'm having the same problem on Windows 2000 with Apache 2. I suspect it's my recent install of ActiveState 5.8 that altered the Windows Registry so ScriptInterpreterSource Directive is no longer working -- but I would very much appreciate any clues!
- Re:Did you manage to fix this? (Score:1)
  
  by shockme (2685)
  
  I don't have a clue about Windows. Sorry.
  
  --
  If things get any worse, I'll have to ask you to stop helping me.
  - Re:Did you manage to fix this? (Score:1)
    
    by tarquin (5005)
    
    How did you fix it on your OS? It might be the windows registry thing is a false trail.
    - Re:Did you manage to fix this? (Score:1)
      
      by shockme (2685)
      
      Heh. Good point. I had a duplicate virtual host entry in my httpd.conf (i.e., one for the "world" interface and a second for the intranet interface). I put a firewall in, thus making the "world" interface section inapplicable. However, the changes I was making were to the "world" section of httpd.conf and not the intranet section (which, because of the firewall, was the only section Apache was now using). Once I removed the "world" section from httpd.conf, everything started working.
      
      --
      If things get any worse, I'll have to ask you to stop helping me.