Not dumb at all, just something Astaro ( US Support anyway ) does not see as an issue. After numerous e-mails trying to explain to them WHY it is a problem to have the firewall show the user an info page with incorrect info on it, and to not be able to change this info without voiding your " warranty ", they ( US Support ) sent me the following information to shut me up. And it worked. Just stayed with version 4.xx at work to avoid the issue entirely.
----------------------------------------------------------------- In /var/chroot-squid/etc/squid.conf-default,
Find the following: # ADMINISTRATIVE PARAMETERS # ------------------------------------------------------------------------ -----
# TAG: cache_mgr # Email-address of local cache manager who will receive # mail if the cache dies. The default is "webmaster." # #Default: # cache_mgr webmaster
Uncomment the cache_mgr and replace webmaster with admin@yourcompany.com or whatever you require.
Is this the right way to do it? Hell no. But it was the answer I was given, and apparently the only current way to make the change. Evidently there are some higher priority bugs they want to fix before they mess with this setting. And honestly, that's fine. Just admit it's broke and add it to the list of things to fix. Hell, I would rather they fix the HTTPS problems first anyway. Getting tired of having to disable the HTTP proxy to pay my bills on-line.
It's just frustrating to know that you could go back through the message base and find that there have been NUMEROUS questions on this issue since 5.xx was released, and here 17 patches later you still have no way of editing the cacheadministrator password through the GUI. What was wrong with the way it worked in 4.xx? It put the administrator e-mail in there, instead of " webmaster ".
Anyway, not a dumb question. Just one they don't want to address.
Astaro is aware that customizing the error pages is important, especiall in larger companies. Nevertheless, this is not included in ASL V5, but it made it to a feature request to be added to asl in the future.
We currently have more the 300 feature requests from customers which we need to track, prioritize and schedule for development. Even if it might see from the outside that Astaro is ignoring this issues, this is not the case.
We fixed the local-nat bug in 5.013, which prevented accessing the DMZ from the pro proxy.
We also have a new up2date package in the pipeline the will improve the proxy performance dramatically. SO plz stay tuned.
Astaro is aware that customizing the error pages is important, especiall in larger companies. Nevertheless, this is not included in ASL V5, but it made it to a feature request to be added to asl in the future.
We currently have more the 300 feature requests from customers which we need to track, prioritize and schedule for development. Even if it might see from the outside that Astaro is ignoring this issues, this is not the case.
We fixed the local-nat bug in 5.013, which prevented accessing the DMZ from the pro proxy.
We also have a new up2date package in the pipeline the will improve the proxy performance dramatically. SO plz stay tuned.
I understand how hard you guys are working, and I appreciate it.
But, I do not understand how you can call this a feature request. The " feature " is already there. It's broke.
Just for the record, we have 9 different webmasters for 9 different sites passing through our firewall. If I catch either of them messing around in my firewall I am going to take their keyboards! :-)
