207576 - Publishing to URL directory (./) should map to index page (./index.html)

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[benc]

STEPS:

Edit any "directory" page in HTTP.
Hit publish.

EXPECTED:
It would be nice if publisher would realize that nobody has real pages that end
w/ "/" in the filename. Instead, it should offer to automatically add
"index.html" to the URL.

OBSERVED:
You have to add the filename yourself, or risk publishing to a destination that
will not work.

Comment 1

[tenthumbs]

But the name could be index.htm or default.htm or whatever. There's no
way for mozilla to know what the server's default is.

Comment 2

[Stewart Gordon]

It would need to use FTP or something anyway, wouldn't it?  So why not retrieve
a directory listing with it and find out?

Comment 3

[benc]

We could add some site-specific info, where you know the index page per site...

Comment 4

[Kathleen :Brade]

Ben--The (weak?) rationale for not providing "index.html" when no file name is
in url being edited is because "index.html" may not be the default for that http
server.  The default might be "index.htm" or "starthere.html" or something else
(as tenthumbs points out in comment 1).

Note that if there isn't a file name specified you can't actually publish
(you'll get a warning dialog).

Stewart (comment 2)--no, using FTP isn't a requirement and may not be available
so that isn't an option to consider.

-->future

Comment 5

[Stewart Gordon]

> Ben--The (weak?)  rationale for not providing "index.html" when no
> file name is in url being edited is because "index.html" may not be
> the default for that http server.

That's exactly what Ben was basing his comment on.  Isn't it reasonable for "index.html" 
to be provided as the default?

> Stewart (comment 2)--no, using FTP isn't a requirement and may not
> be available so that isn't an option to consider.

That's like saying "I'm not going to go and buy some milk because they just might be out 
of stock".

Whatever other publishing methods there are that don't support directory listing, what 
have you against using FTP, _if_ it is what's being used, to find out?

Comment 6

[benc]

brade was correct here... This was an offshoot of a really strange RFE for
Networking:file, so I should have mentioned comment #3 in the original proposal.

I think if you glue those comments together this feature makes sense, after all,
someone that publishes to a site should know what the default page mapping is...

I don't think we should use FTP to scan the directory, because there is no
assurance that http:// maps to ftp:// on a site.

Comment 7

[Stewart Gordon]

But if FTP is being used to publish pages, of course it needs to know what FTP path it's 
going to upload to.

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420