There is no error printed it just says that it can't open the file based on the path

File open errors do not print by default. You must specifically put something along the lines of "or die $!" after the open.

I know I could use a link to the file like "../info.txt" but it doesn't open the file, unless the path is absolute to the file.

Where did you get that idea? Of course you can use . and .. directories in a path to a file for opening.

Since you don't state where the files' directory is relative to the cgi-bin directory, it is difficult to give very precise advice. However, in general, use ../ to go up one level in the directory hierarchy and the exact directory name to go down.

Say you have a directory structure like this:

|--apache2--|---cgi-bin
            |
            |---htdocs
            |
            |---images

or whatever. To access a file from the htdocs directory, starting at the cgi-bin directory, you would specify: '../htdocs/info.txt'. Substituted back into your script:

use warnings;
use strict;

$0 =~ '(.*[\\\/])\w+\.\w+$';
my $curr_dir = $1 || "./";

# Note, you would be much better off with
# use Cwd;
# and 
# my $curr_dir = cwd();

$info_file =  $curr_dir . '../htdocs/info.txt';

open my $fh, '<', $info_file or die "Could not open file, $!";
while (my $line = <$fh>){
    #process line
}
[download]

Your code doesn't work, here is what I am trying:


use Cwd 'chdir';
chdir "../htdocs/";

open (FILE, "<$ENV{'PWD'}info.txt") || print "There is no file here in
+ $ENV{'PWD'}info.txt";
while ( my $line = <FILE> ) {
  chomp($line);
  #code....
}
[download]

Sigh. My fault for posting untested code.
You are still missing the point about using Cwd. You don't need the chdir and you shouldn't rely on $ENV{PWD}. Here is a (tested) version showing what I mean.

use warnings;
use strict;

use Cwd;
my $curr_dir = cwd();

my $info_file = $curr_dir . '/../htdocs/info.txt';

open my $fh, '<', $info_file or die "Could not open file, $!";
while (my $line = <$fh>){
    # process text
}
[download]

I don't do windows, but that file

${curr_dir}info.txt
[download]

open (FILE, "<"$curr_dir/info.txt")
[download]

open (FILE, "<..\\htdocs\\info.txt") || print........
[download]

Yes it's Windows, it didn't work like that.

If this would work on windows:

open (FILE, "<..\\htdocs\\info.txt") || print........
[download]

then this would also work on windows:

open (FILE, "<../htdocs/info.txt") || print........
[download]

Well it's windows what more can i say.....

I'll let you decide ... but nothing would probably be appropriate.

---

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?

"Science is about questioning the status quo. Questioning authority".

The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.

That's way I am going trough this because this line of code,


open (FILE, "<../info.txt") || print "There is no file here info.txt";
[download]


doesn't work unless it has a absolute link, and I can't have it like that, it has to be relative.