File size issues

[Sean Conner]

It was thus said that the Great solderpunk once stated:
> >   I had a thought last night in that there does, in fact, exist a way to
> > include the information without changing the syntax of the protocol.  The
> > MIME type that is returned can have parameters, and these parameters can act
> > as small headers, so:
> > 
> > 20 text/plain; charset=iso-8859-1; size=1345
> > 20 text/gemini; size=2003; modified=2019-08-18T17:15-05:00
> >
> 
> Strictly speaking, those parameters are supposed to be limited to the
> ones defined in the RFC for the corresponding type, right?

  Nope.  From RFC-2045, section 5:

	MIME implementations must ignore any parameters whose names they do
	not recognize.

  Also, from the same section:

	The ordering of parameters is not significant.

> Not that we're necessarily playing by all the rules here.  text/gemini
> is an unregistered, experimental type and so I think strictly speaking
> we should be text/x.gemini or text/prs.gemini or something...

  Nope, RFC-6648 deprecates the whole "X-" thing.

  -spc