Links to standard (card, calendar, geo) schemas incorrect

[evert]

[Relequestual]

Where exactly? Looks like they are valid on the home page and in one of the examples for me.

[evert]

The links in the bottom here:

http://json-schema.org/documentation.html

Link to stuff like this:

http://json-schema.org/geo

Opening that link in firefox at least shows it as a BIN file, and looking in the developer console I'm getting a hexadecimal sequence for some reason.

Inspecting it further: not sure why I'm getting the weird output in firefox, but if I try that url with curl I did notice an incorrect mime-type, which is probably the root cause for the weirdness.

[Relequestual]

I'm using Firefox and not experiencing that problem. It opens as a text file for me when downloaded.

[evert]

@Relequestual that's surpising as the Content-Type is wrong and there's no standard file extension, and no Content-Disposition with some hint as to how a browser should handle a download. Given those facts, a browser treating those links as text-files would actually be the unexpected behavior ;) See curl -v http://json-schema.org/geo to double-check.

My browser is a fairly stock firefox browser. I can't imagine I'm alone. How about fixing Content-Type for a slightly saner response?

[Relequestual]

@evert Hum. For my version of firefox, it downloads as standard, and suggests opening as text.
I'm not sure how I would go about setting the content type for the file beyond appending .json to the filename.
Pull request welcome if you know a different way.

[evert]

Ah I didn't realize you were using Jekyll. In that case I would indeed argue that you should add .json to these files to force a correct mime-type. I'd be happy to submit a PR for this if you'd like.

[Relequestual]

If you wouldn't mind, that would be helpful. I don't have the time today (or this week) to checkout the repo to make this change site wide. Thanks =]

[awwright]

@evert The URIs were purposefully selected to not use filename extensions, and we can't really change them without breaking things

Are you aware of any way to send a 200 with Content-Type: application/schema+json with Jekyll?

[evert]

@awwright jekyll just generates files. It's a static file generator and thus has no control over content-types. It's not aware of HTTP at all. Basically your two options are:

1. Keeping the url
2. Having a correct content-type

Both is unfortunately not possible

[Relequestual]

@awwright out of interest, why were they slected to not use extensions?

[Relequestual]

@awwright ping!

[awwright]

@Relequestual Filename extensions have a history of being left off URIs sometimes... idk if there was any rationale for it here, but it's something that's supposed to be supported by web servers and GitHub doesn't. https://www.w3.org/Provider/Style/URI.html#remove has some background.

A slightly more pressing issue is that we can't serve any file with application/schema+json regardless of what filename we pick.

[Relequestual]

I think that's a limitation on jekyll - it picks the content type based on the file extension, I believe. I read this somewhere recently