"pub serve" should support index.html and directory listing

[nex3]

It's a common convention for servers to serve "/dir/index.html" when a user requests "/dir" or "/dir/". "pub serve" should follow this convention as well.

[nex3]

Issue #15622 has been merged into this issue.

[jmesserly]

also directory listing :)

---

Changed the title to: ""pub serve" should support index.html and directory listing".

[munificent]

What semantics do we want here? If you request "foo/bar" that could either be:

1. Request the asset "bar" in the directory "foo".
2. Request "index.html" in the directory "foo/bar".

Is the idea that we try 1 and if it fails with an asset not found, we then try 2?

[nex3]

Implementation-wise, that seems right. Semantically, it's not possible for an asset and a directory named "foo/bar" to exist at the same time.

[munificent]

Removed Type-Defect label.
Added Type-Enhancement label.

[munificent]

Removed Priority-Unassigned label.
Added Priority-Medium label.

[munificent]

Marked this as blocking #15859.

[munificent]

Unmarked this as blocking #15859.

[munificent]

Marked this as blocking #15830.

[sethladd]

How much of a web server is pub serve? (Not rhetorical, I don't understand the scope) We have the http_server package which does virtual directories, index.html resolution, mime types, etc. Is pub serve supposed to provide all those services or could it act as a "filter" or "handler" when a request needs something transformed in real time?

[sethladd]

cc @kevmoo.

[nex3]

Is pub serve supposed to provide all those services

Ideally we'd like "pub serve" to support index.html and mime types for sure. I'm less keen on virtual directories.

could it act as a "filter" or "handler" when a request needs something transformed in real time?

I'm not sure what this means. Can you give an example?

[munificent]

Added DevStory label.

[nex3]

Issue #16438 has been merged into this issue.

[nex3]

Set owner to @nex3.
Added Started label.

[nex3]

Fixed by r32615.

---

Added Fixed label.

[DartBot]

This issue has been moved to dart-lang/pub#716.