[FFmpeg-devel] Cross-origin resource error on fate.ffmpeg.org
Michael Niedermayer
michaelni at gmx.at
Wed Sep 17 21:59:26 CEST 2014
On Wed, Sep 17, 2014 at 11:33:32AM -0700, Daniel Verkamp wrote:
> Hi FFmpeg web folks,
>
> When visiting http://fate.ffmpeg.org/ using a browser that enforces
> CORS[1], loading the FontAwesome icon font causes this error:
>
> Font from origin 'https://ffmpeg.org' has been blocked from loading
> by Cross-Origin Resource Sharing policy: No
> 'Access-Control-Allow-Origin' header is present on the requested
> resource. Origin 'http://fate.ffmpeg.org' is therefore not allowed
> access.
>
> The fateserver commit that introduced this (b74b380b) includes this change:
>
> > diff --git a/index.cgi b/index.cgi
> > index 7204591..105cb86 100755
> > --- a/index.cgi
> > +++ b/index.cgi
> > [...]
> > print "Content-type: text/html\r\n";
> > +print "Access-Control-Allow-Origin: https://ffmpeg.org\r\n";
>
> However, this won't help, since the Access-Control-Allow-Origin header
> needs to be on the requested resource (in this case,
> fontawesome-webfont.*), not the requester.
>
> To make fate.ffmpeg.org work correctly, the above header would need to
> be added to the web server configuration for the files in
> ffmpeg.org/fonts with http://fate.ffmpeg.org (or *) as the allowed
> origin.
as you seem to know this / have researched it already
can you post what i need to add to httpd.conf to make this work ?
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The greatest way to live with honor in this world is to be what we pretend
to be. -- Socrates
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20140917/9f501d4a/attachment.asc>
More information about the ffmpeg-devel
mailing list