| Author |
Message |
   
Mike H
Unregistered guest
Rating: N/A
Votes: 0 (Vote!) | | Posted on Sunday, January 27, 2002 - 07:24 pm: | 
|
I'm running on a unix server, and what I've noticed is that any script that looks properly formatted when opened in notepad is viewed as "corrupted" by my server and will return "premature end of script headers" errors.
Ironically, for Discuss, the windows .zip version has the perl files in the 'proper' format...but both versions of ftpdiag.cgi are of this corrupted format. I'm not using notepad to edit my files; I use another editor...but I use it as a test to see if it's got those nasty carriage returns.
I think this is why several people on this forum are having problems with ftpdiag that they can't figure out....and neither can I. Is there a version of this file that looks nasty in notepad for me? 
Thanks...mike |
Kevin P.
Moderator
Username: Paulisse
Post Number: 5816
Registered: 11-1999
Rating: N/A
Votes: 0 (Vote!) | | Posted on Monday, January 28, 2002 - 10:16 am: |
|
If you upload the files in ASCII mode and your server is unix, with a properly functioning FTP client, the carriage returns are removed and converted to newlines.
By "properly functioning FTP client" I mean one where you can actually select ASCII or binary mode transfer, and have your setting actually be used. WS_FTP is one popular FTP client that works properly. Cute FTP is one FTP client where some versions tend to forget about whether you've selected ASCII or binary and instead bases the transfer mode decision on your predefined list of extensions. |
mike h
Unregistered guest
Rating: N/A
Votes: 0 (Vote!) | | Posted on Monday, January 28, 2002 - 05:37 pm: |
|
I'm using WS FTP LE- and I always have ascii selected for uploading these kinds of files. For some reason, if they are downloaded with the carriage returns, they stay that way for good, at least on my system.
I'm waiting to hear back from my web host's technicians, because I'm getting convinced it's something strange on their (my) end.
Any other ideas? |
Kevin P.
Moderator
Username: Paulisse
Post Number: 5856
Registered: 11-1999
Rating: N/A
Votes: 0 (Vote!) | | Posted on Monday, January 28, 2002 - 06:54 pm: |
|
Many zip programs (e.g. WinZip) automatically convert the unix linefeeds into the Windows CR+LF upon extraction. This conversion is undone when the file is uploaded back to the server in ASCII mode. If uploading the file in ASCII mode to the server results in problems because the file has carriage returns, then something is wrong with the ASCII mode transfer. None of this really has anything to do with Discus (hopefully the web host can figure out what's wrong). |
Anonymous
Rating: N/A
Votes: 0 (Vote!) | | Posted on Saturday, December 07, 2002 - 10:17 pm: |
|
I am a web host and am having the same issues for a client of mine. I use ws-ftp pro... there is definitely some sort of problem with the file. Nothing fixes this so far as I can tell... going to have to telnet in to see what happens... |
pinwheel
Unregistered guest
Rating: N/A
Votes: 0 (Vote!) | | Posted on Saturday, December 07, 2002 - 10:47 pm: |
|
as a side note... i tried out the non beta version and it works no problem... maybe this is a problem with the beta version of the script... |
Kevin P.
Moderator
Username: Paulisse
Post Number: 9867
Registered: 11-1999
Rating: N/A
Votes: 0 (Vote!) | | Posted on Sunday, December 08, 2002 - 10:51 am: |
|
There are not any known problems with the script, and it's been run successfully thousands of times. You could get some helpful information by running it from the command line, like it suggests in step 5 of this:
http://support.discusware.com/center/resources/errors/500ftpdiag.html
But as it says there, "Then again, if you have telnet access, you might consider why you are running the FTP setup procedure..." |
Download
Purchase
Contact Us
Download
Purchase
Contact Us