[Koha-bugs] [Bug 20397] Implement Content Security Policy

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20397

--- Comment #11 from Jake Deery <jake.deery at ptfs-europe.com> ---
Thank you, so far it's been very mild, so thankfully I'm feeling I will pass
through it quickly and be able to return to normality soon!

That's a valid point! Plus, provided the file is being stored somewhere that is
unlikely to be touched, it shouldn't be an issue (assuming the static file
route is chosen).

I believe this is the case, too, using Memcached? While this is definitely
beneficial from a performance standpoint, if delivering via a Perl script is
chosen, it still wouldn't be quite as fast as using static files with 'Expire'
headers set in the Apache2 config.

In theory - the weight of Perl could be reduced a bit by moving this stuff out
to static files! But it does come with the downside of having to manage the
static file, and handle the behaviour quirks of that file being managed.

My experience in Koha is still quite new - so I don't know how good it is at
things like file management and database access! Do you think Koha/Perl is
performant enough to make the benefit of static files worthwhile? And do you
think on busier systems, the reduction of frequent dynamic requests to a Perl
script would be beneficial enough to warrant a static file in place of a Perl
script request?

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.