sanoyes
join:2000-10-31
Lees Summit, MO | reply to sanoyes
Re: How do I allow D/L from HomePage? NotWorking okay, marti/and on further review....
I took off all the files and put only one file up...
renamed it wstabs00.ex_ and I was successful in downloading it.. it still had an error when I named it wstabs00.exe..
Now I will put my other file up and see how it works...
The 3meg size is a hindrance, and I thought I got 10megs..
oh well..
Thanks for the help, and I hope this might help other people...
sanoyes - lees summit |
|
|
|
 martiColor outside the linesPremium,MVM
join:2001-12-14
Houston, TX
kudos:5 | reply to sanoyes
Have you found out why the file wouldn't download before? I just went to your link and finally got the d/l box (IE6).
Progress... |
|
 dffisherUpon Closer Inspection
join:2001-08-30
Rockwall, TX | reply to sanoyes
said by sanoyes:
it still had an error when I named it wstabs00.exe..
When uploading the file on your PC named wstabs00.exe, were you ever able to determine just how that file appeared on your website? Same or different name? What directory folder? Did you use NetObjects Fusion to do the upload?
I guess that I'm still wondering why a file with an "exe" extension won't work on the home.swbell.net server. Is it swbell, or is it NetObjects Fusion.
--
SWBell DSL and Prodigy - Router, HPNA, Phone Wiring: »pages.sbcglobal.net/dffisher/DSL/ |
|
 sadowskiI Am My Own DoppelgangerPremium,MVM
join:2000-04-14
Buffalo, NY | reply to marti
said by marti:
Have you found out why the file wouldn't download before?
Everyone seems to be overlooking the most obvious of clues. The error page when the extens were .exe was a cgi error. It appears the server was trying to execute the files. This is common amongst FP servers which is why I brought that up. If they aren't running the FP extensions then I don't know why it tried to run the apps. |
|
dffisherUpon Closer Inspection
join:2001-08-30
Rockwall, TX | said by sadowski:
It appears the server was trying to execute the files. This is common amongst FP servers
Good thought. I'm not even sure how current the home.swbell.net FAQ is, even if they do say "Microsoft Frontpage Extensions are not supported at this time", and "Personal Home Page does not include support for custom CGI executables". But they do have a CGI counter, so something could be trying to run the exe. In the meantime, I'm still waiting for someone to answer sanoyes questions about it at the swbell.homepages Newsgroup.
--
SWBell DSL and Prodigy - Router, HPNA, Phone Wiring: »pages.sbcglobal.net/dffisher/DSL/ |
|
dffisherUpon Closer Inspection
join:2001-08-30
Rockwall, TX | reply to sadowski
Update:
It's pretty well confirmed now that the HTTP 500 error was caused by the server's attempt to run the uploaded EXE file when the page link was clicked. Another home.swbell.net subscriber was kind enough to run a test for me on his Personal Home Pages website, but using SBIS page manager instead of NetObjects Fusion to do the upload. Clicking the link on his page also resulted in HTTP Error 500.
All of this is in contrast to the result obtained when uploading and browser-downloading an EXE from the pages.sbcglobal.net Personal Web Pages server, which does not produce an error. However, a follow-up test I conducted using a file with a CGI extension on my pages.sbcglobal.net site did produce the HTTP 500 error.
The test results make suspect all executable file types for browser downloading, including EXE, CGI, BAT, PL, and SH. As you all suspected, it's best to either "Zip" them, or rename them, if you want to download them using a browser.
--
SWBell DSL and Prodigy - Router, HPNA, Phone Wiring: »pages.sbcglobal.net/dffisher/DSL/ |
|
sadowskiI Am My Own DoppelgangerPremium,MVM
join:2000-04-14
Buffalo, NY | That's very odd that it would try to execute all that stuff. It's like the whole site is one big scriptalias.  I hope they at least have file permissions set securely so that no one can take advantage of this, assuming that a proper binary for the OS could actually execute. |
|
dffisherUpon Closer Inspection
join:2001-08-30
Rockwall, TX | said by sadowski:
That's very odd that it would try to execute all that stuff.
I think you're right. The PHP account owners do not have permission to set file attributes to "execute". What probably really happens is that the OS sees that the file type is mapped to CGI, tries to run it, then chokes because the file is not executable. And I have to admit that I didn't try all the extensions I listed; it's just that I've noticed that those are the ones most often associated with CGI scripting. I find it equally as strange though that SBC just hasn't set up a single folder for CGI, instead of having the OS choke no matter where the script is uploaded.
--
SWBell DSL and Prodigy - Router, HPNA, Phone Wiring: »pages.sbcglobal.net/dffisher/DSL/ |
|
sadowskiI Am My Own DoppelgangerPremium,MVM
join:2000-04-14
Buffalo, NY
| All I found it is
The site home.swbell.net is running Netscape-Enterprise/3.5.1B on Solaris.
I'm going to try Verizon's (Former BA) and see if they do anything weird like that.
Exact same server software and os and result here on members.bellatlantic.net
[text was edited by author 2002-01-16 12:22:30] |
|
dffisherUpon Closer Inspection
join:2001-08-30
Rockwall, TX | Even more confusing. Going directly to members.bellatlantic.net results in the now-familiar HTTP 500 error. Going instead to members.bellatlantic.net/index.html gets their menu page, but with a "Page Not Found" title. Many of the links call CGI scripts, but most of the links appear to be broken (or I just don't have permission somehow). I couldn't even pull up their FAQs on that site. I guess I'm not surprised when you said that you couldn't download EXE files from their Personal Web Page Service.
--
SWBell DSL and Prodigy - Router, HPNA, Phone Wiring: »pages.sbcglobal.net/dffisher/DSL/ |
|
sadowskiI Am My Own DoppelgangerPremium,MVM
join:2000-04-14
Buffalo, NY | Could be then that the page is really their standard error page but designed to discourage spiders and other creepy crawlers, and users from writing/calling-in. Less likely is that their error page is cgi generated and there's a fault there. |
|
