Closed Bug 138649 Opened 23 years ago Closed 23 years ago

publish does not work for Linux RH 7.2 and Apache server

Categories

(SeaMonkey :: Composer, defect)

Product:
SeaMonkey
Component:
Composer
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: sujay, Assigned: Brade)

Details

(Whiteboard: publish)

I was at Sarah's cube last week and apparently she's trying to publish to an interesting configuration: Apache web server on Linux RH 7.2. Publishing just doesn't work. Sarah, can you include the error messages or dialogs that come up. thanks. Akkana, I heard you're running a similar configuration. can you please try publishing up a simple document to this type of server.
Also sarah, it was ftp publish that you tried, right? thanks!
If this problem is with Apache web server, then this isn't an FTP publishing bug (or am I missing something? Does Apache have an ftp server?). Are you able to use 4.x to publish to this server?
here are the steps i took for http publishing, using 2002.04.22.08-1.0.0 (branch, commercial) bits on linux rh7.2. i have Apache 1.3.20-16, which iirc is the default version of the web server i got when i had upgraded to Redhat 7.2. 1. in composer, created and saved a simple web page called "la.html" --i had saved it to my home dir (/home/halo/la.html). 2. select File > Publish. 3. in the Settings tab, enter the following: Site Name: Hopey Publishing URL: http://hopey.mcom.com/foo/ HTTP address to browse to: http://hopey.mcom.com/foo/ 4. go to the Publish tab, enter/confirm the following: Page Title: la [prefilled] Filename: la.html [prefilled] * deselected the checkbox for "Include images and other files" 5. go back to the Settings tab, enter my User name (halo) and passwd --did NOT select the "save password" checkbox. 6. clicked the Publish button. results: failed to publish the file. Publishing to Site: Hopey Site URL: http://hopey.mcom.com/foo/ Publishing Status: Some files failed to publish [la.html is in a listbox with a red 'X' next to it, denoted as "Failed"] this shouldn't be a permissions problem, since i (as 'halo') owns that directory (/var/www/html/foo/, set as 755). very odd.
i'm going to try to publish via http from another machine, then later on test via ftp...
got the same results (failure) when using 2002.04.22 branch commercial bits on Mac 10.1.4 and win2k. (used the same steps as in comment 3.)
Sairuh is going to try publishing with 4.x (in case the server hasn't been configured to accept publishing)
hmm, maybe my server is misconfigured, as kathy pointed out: i cannot publish using communicatory 4.78 (linux). get the following error: Forbidden: You don't have permission to access /foo/la.html on this server. i had entered "http://hopey.mcom.com/foo/la.html" for the publishing location. (i haven't published with 4.7x in *ages*, so not sure if what i entered was correct.) will discuss apache settings with akkana...
ftp publish doesn't seem to be working properly, but i'm not sure if i'm encountering a known bug, or doing something wrong. 1. edit the same page as in comment 3. 2. select File > Publish. 3. enter the following for the Settings tab: Site Name: Hopey Publishing URL: ftp://hopey.mcom.com/ [since the file is in my home dir] HTTP address to browse to: http://hopey.mcom.com/foo/ 4. keep the same settings in the Publish tab, click Publish button. results: the progress dialog says, "Publishing completed", and there's a green checkmark next to la.html. however, "la.html" was NOT published (copied over) to the target location. ie, "la.html" doesn't exist at /var/www/html/foo/ (or, http://hopey.mcom.com/foo/).
I can publish to an ftp url with a branch build 2002041617. Apache on Redhat 7.2 seems to be configured off by default, and in addition, http put is off in by default in the config file (as you might expect). So it sounds like the current problem is just that put isn't enabled on the machine in question. There are some commented-out lines in /etc/httpd/conf/httpd.conf involving http put, most of which look straightforward except the part about wanting a separate password file. I'm getting an error (but it doesn't tell me what the error is) when I try to start the http server on my own 7.2 machine, so I haven't succeeded in getting a server working to try enabling http put. I'll keep poking at it.
resolving this as invalid (at least for the time being) Please reopen if there is a problem with publishing to Apache's web server when PUT has been enabled.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Whiteboard: publish
verified.
Status: RESOLVED → VERIFIED
John/Shiva/Akkana, any of you able to enable "put" on your Apache Server? If so let us know in this bug report. thanks.
Tom what about you?
Let me know how to enable it and I can enable it in my machine.
Akkana, how do you enable "put" on the apache server? thanks.
Like akk noted above, look in httpd.conf for the lines that set up a sample PUT configuration (search for 'mod_put' and or 'Netscape Gold'). Just uncomment those lines, then run 'htpasswd -bc putusers putter birdie', then restart the httpd.
If you look at /etc/httpd/conf/httpd.conf on Redhat 7.2 you see a bunch of lines commented out like this: # # Allow http put (such as Netscape Gold's publish feature) # Use htpasswd to generate /etc/httpd/conf/passwd. # #<IfModule mod_put.c> # Alias /upload /tmp # <Directory /tmp> # EnablePut On # AuthType Basic # AuthName Temporary # AuthUserFile /etc/httpd/conf/passwd # EnableDelete Off # umask 007 # <Limit PUT> # require valid-user # </Limit> # </Directory> #</IfModule> Presumably, uncommenting this section and restarting httpd (/etc/init.d/httpd restart) will enable http put. I don't know whether you need to run htpasswd first; sairuh says she has used that program, so perhaps she can elaborate. I can't test it here, though, because /etc/init.d/httpd start on my 7.2 machine (I did select Web Server when I installed) exits with error 1 and no further explanation. I don't know what its problem is.
If jrgm's suggestions don't work, this might help: http://httpd.apache.org/docs/misc/FAQ.html#putsupport
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.