[wp-meta] [Making WordPress.org] #151: Plugin images are sent with wrong Content-Type
Making WordPress.org
noreply at wordpress.org
Sun Sep 1 22:15:11 UTC 2013
#151: Plugin images are sent with wrong Content-Type
---------------------+-------------------------------
Reporter: toscho | Owner:
Type: defect | Status: new
Priority: normal | Component: Plugins Directory
Resolution: | Keywords:
---------------------+-------------------------------
Comment (by samuelsidler):
Replying to [comment:2 nacin]:
> Wontfix? Serving application/octet-stream isn't a dealbreaker, forcing
svn:mime-type on pre-commit is lame, and I'd rather not write a bot for
it. Systems might have another idea but I doubt it.
Why is it lame to force it on pre-commit? For a select set of filetypes, I
don't see it as a bad thing.
Replying to [comment:3 toscho]:
> I don’t know much about SVN, so just for clarification: Can the plugin
author set the proper MIME type in her/his own repository per SVN? In that
case, a short how-to on the [http://wordpress.org/plugins/about/svn/
developer SVN page] would be helpful.
Should be able to, yes.
This command should do it:
{{{
svn propset svn:mime-type image/png *.png
svn propset svn:mime-type image/jpeg *.jpg
}}}
Alternatively, plugin authors can set this in their ~/.subversion/config
file:
{{{
*.png = svn:mime-type=image/png
*.jpg = svn:mime-type=image/jpeg
}}}
That'll apply to only new files though. Fixing already-committed files
will require the command above.
--
Ticket URL: <http://meta.trac.wordpress.org/ticket/151#comment:4>
Making WordPress.org <http://meta.trac.wordpress.org/>
WordPress blogging software
More information about the wp-meta
mailing list