added two parameters: only-get-or-head and check-index

[tts-sdrissen]

Description

I am using your project to mock an API for testing purposes.
I needed two more functions to make it work.

Problem

I need to test API requests to something like /users/1 AND /users/1/profile .
So what I did was creating a folder structure and placed in the "/users/1"-folder an index.html
But it returns a directory listing even if a index.html is present.

And I need POST requests, but the original code blocks them.

Solution

Introduced parameter check-index for looking for index.html, before return directory listing.
Introduced parameter only-get-or-head to allow to set it to false, to ignore method check.

Notes

If you merge this, nothing significant will happen for existing users, because the default parameters say not to use the functions introduced in this request.

[Eun]

Thank you for your contribution! 👍
I see the usecase.
I also would like to see the feature implemented, however I think there are some problems with long time use of the features you added.

1. When introducing an index handler it is required that the index file can be specified. (Some users use index.html, others use index.htm)
   The best solution would be to add an array parameter where devs could specify what should be handled:
   index-files: [index.html, index.htm]
   1.1. Making the directory listing configurable would be the next logical step when adding an index handler.
2. The "only get or head" feature should follow the same pattern:
   allowed-methods: [GET, HEAD]

Let me know if you intend to make the changes. 😃

[tts-sdrissen]

Nice to see, that you reviewed my pull request!
I think that your comments are reasonable and I started to make the changes you suggested.

I committed "requested changes" and I can see it in this pull request - not sure, if you can see it, too.
But it is not tested yet... I will approve it, as soon as my Github Action for another projects ran without an issue.

[tts-sdrissen]

Okay, the requested modifications are working.
And you should see the commit "requested changes" and "minor fixes".

Be aware, that I modified the README in "my" repo for copyright reasons.
Better check every file before merge 😅

[Eun]

Thanks, for the work! 💪
I checked the code, just one tiny bug, a bit of cleaning up. Then I would love to merge 😃
I suggested all the changes so you just need to accept them 👍

[tts-sdrissen]

I approved the changes and found an error in the README.md - Tabs instead of spaces.
After you merge those changes, can I delete my fork?

[Eun]

Yes you can delete your fork, thanks again 👍

[tts-sdrissen]

It even says "If you wish, you can delete this fork of Eun/http-server-action in the settings."

It was a pleasure to collaborate with you.