Re^2: Using a 2000 Box to Access an Include File from 2003

I have anon access turned off and tried both Window digest and Integrated Authentication (preferred). I would like to stay away from having user credentials in the script itself, but if theres no other way then...

Will check the logs for more info. Thanks.

Update: Checked the logs and event viewer and theres nothing pertinent in there.

Comment on Re^2: Using a 2000 Box to Access an Include File from 2003

Replies are listed 'Best First'.
Re^3: Using a 2000 Box to Access an Include File from 2003 by NetWallah (Canon) on Jun 18, 2004 at 06:04 UTC
OK - I think I know why the second script (with LWP) fails: You are accessing a file with a .inc extension - by default, the web server does not associate this extension with a MIME type, so it will give you some kind of error. To fix this, associate .inc with text/html - however - I must warn you that this is a security hazard, since users will now be able to view your .inc scripts. Accessing the file via \\Server\path should work - make sure you have escaped back-slashes. Try the "-e <Filename>" test to verify file existance, and print the file name to see if it does look like it is supposed to. Remember - if you use a drive-letter like \\Server\c$ , you need to escape the dollar-sign as well. sweetblood and others messages above also have valid points, but I have not seen your response to them. Offense, like beauty, is in the eye of the beholder, and a fantasy. By guaranteeing freedom of expression, the First Amendment also guarantees offense.	[reply]

Replies are listed 'Best First'.

Re^3: Using a 2000 Box to Access an Include File from 2003
by NetWallah (Canon) on Jun 18, 2004 at 06:04 UTC

You are accessing a file with a .inc extension - by default, the web server does not associate this extension with a MIME type, so it will give you some kind of error.

To fix this, associate .inc with text/html - however - I must warn you that this is a security hazard, since users will now be able to view your .inc scripts.

Accessing the file via \\Server\path should work - make sure you have escaped back-slashes. Try the "-e <Filename>" test to verify file existance, and print the file name to see if it does look like it is supposed to. Remember - if you use a drive-letter like \\Server\c$ , you need to escape the dollar-sign as well.

sweetblood and others messages above also have valid points, but I have not seen your response to them.

Offense, like beauty, is in the eye of the beholder, and a fantasy.
By guaranteeing freedom of expression, the First Amendment also guarantees offense.

[reply]