While I understand that it is not recommended to run other virtual servers on an IPA machine, it's not always achievable, nor necessary in trustworthy environments.
But having:
Header unset ETag
in /etc/httpd/conf.d/ipa.conf unsets ETags for all other virtual servers on the same host. It would be nicer in the spirit of co-existence if that could be moved to somewhere specific to the IPA virtual server only so that IPA is not setting HTTP policy for all virtual servers on the same installation.
/etc/httpd/conf.d/ipa.conf
ETag
Out of curiosity, what type of app you run on IPA server?
The fact, that IPA configures a lot on httpd is not the only reason why not run apps on IPA server. The main reason is security. If the app has a security hole(s) then it might endanger security of IPA server which holds sensitives secrets.
A number. But the particular app that is being affected by this issue is Owncloud.
Given that this is really not recommended way, IPA team does not plan to fix it any time soon.
It can be speed-ed up by sending a patch though.
~~I'd be happy to send a patch if somebody can indicate which IPA paths are incompatible with ETag.~~
I created at patch at https://pagure.io/fork/brianjmurrell/freeipa/c/a9fc01c2d2a3a863844bcf86dae79477327d030b and tried to create a PR but got an error:
Page not found (404) With the message:
No pull-request allowed on this project
You have either entered a bad URL or the page has moved, removed, or otherwise rendered unavailable. Please use the main navigation menu to get (re)started.
Are PRs really not allowed against this project?
Hi @brianjmurrell,
we use GitHub to open PRs [1]. Could you open your PR there?
[1] https://github.com/freeipa/freeipa/pulls
Oh. OK. Sure, I can open one there.
https://github.com/freeipa/freeipa/pull/1482
d7c23a3 Move ETag disabling to /ipa virtual server
Metadata Update from @rcritten: - Issue close_status updated to: fixed - Issue set to the milestone: FreeIPA 4.7.1 (was: Ticket Backlog) - Issue status updated to: Closed (was: Open)