wgenial / mimetypeicons-nodejs Goto Github PK

Reproducible steps:

1. Go to https://mimetypeicons-wgenial.rhcloud.com/application/pdf?size=scalable

Expected behavior:
Get a permanent redirect (301) to https://mimetypeicons-wgenial.rhcloud.com/mimetypes-icons/scalable/application-pdf.svg

Actual behavior:
Get a temporary redirect (302) to https://mimetypeicons-wgenial.rhcloud.com/mimetypes-icons/scalable/application-pdf.svg

This saves a RTT if the icon is already cached. The browser refuses to show the icon before and during the request in case of a 301; just to be sure the original URL does not suddenly points somewhere else.

A 302 tell the browser it will not suddenly point somewhere else, and so the browser may cache this entire response.

The linked faenza-icon-theme is no longer on google code. This raises the question if there any plans to keep adding icons for new mime types.

Could you please add the icon for application/json. Generally it should look like "{;}"

.

Thanks.

Reproducible steps:
Go to https://mimetypeicons.gq/.ai

Expected result:
A 20x code with a image.

Actual result:
A 404 with the following HTML content:

Cannot GET /mimetypes-icons/32/application-postscript.png

Reproducible steps:

1. Go to https://mimetypeicons-wgenial.rhcloud.com/something.webp

Expected behavior:
Get a temporary redirect (302)

Actual behavior:
Get a permanent redirect (301)

Unknown types should not get a permanent redirect to the default icon. And this can be considered true too if a available size is missing, eg: request for https://peicons-wgenial.rhcloud.com/doc?size=4

Browsers might honor the 301 redirect forever. And it will be hard to convince them otherwise regardless if we finally have new icons for those new sweet mime-types. A solution would be to issue a 302 in case the direct might change in the future.