Proxy service & allowedDomains

[riogd]

I am trying to test a zimlet I have just made and am running into 403 errors on /service/proxy?
First of all I made a testing COS called ztesting, the only one where I am enabling the Zimlet, for testing purposes.
My config_template.xml has:

		<property name="allowedDomains">*.mydomain.com, *.zimbra.com</property>

(although I believe it may not be read as I can't access the other global properties as described in this other thread)
And I have modifed this testing COS like this:

zimbra@myhost:~/log$ zmprov mc ztesting zimbraProxyAllowedDomains "*.mydomain.com, *.zimbra.com"

Just in case, I even restarted zimbra after making those changes and I am still getting a 403 error.

xx.xx.xx.xx - - [05/Sep/2007:19:28:35 -0700] "POST /service/proxy?target=https://targeturl HTTP/1.1" 403 964 "https://mydomain.com/zimbra/mail" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6"

This is of course shown in Firebug as well.

To help assure that this wasn't just poor coding on my part, I installed ArunaURL, and it is getting the same errors on it's proxy requests.

Can anyone tell where I have erred or is there any more information I can provide to help figure that out ?

Cheers,

RioGD

[riogd]

I believe I have found the problem, and it may be a bug. As reported elsewhere, the config_template only is applied to the default COS. Thus the only way to make Zimlets work under non-default COS's, that I have found, is to manually:

zmprov mc <non-default-COS> zimbraProxyAllowedDomains "*.domain.com"

Now the rather large problem, and what makes this seem even more like a bug, is that although the config isn't applied to non-default COS's, re-deploying the Zimlet wipes out the zimbraProxyAllowedDomains for all non-default COS's. So each time you redeploy the Zimlet you have to go and make that manual change. This is why I was constantly getting 403's, my manual settings kept getting wiped without my knowing it.

If it can automatically wipe my manual settings, it would be nice if it could automatically apply the supplied config settings I want to begin with so I don't need to do it manually I suspect this may also be why I couldn't access the global settings from within the js code, the config_template is probably not accessible from non-default COS's. Time to test that theory now.

Cheers,

RioGD

[JoshuaPrismon]

Originally Posted by riogd

I believe I have found the problem, and it may be a bug. As reported elsewhere, the config_template only is applied to the default COS. Thus the only way to make Zimlets work under non-default COS's, that I have found, is to manually:

zmprov mc <non-default-COS> zimbraProxyAllowedDomains "*.domain.com"

Now the rather large problem, and what makes this seem even more like a bug, is that although the config isn't applied to non-default COS's, re-deploying the Zimlet wipes out the zimbraProxyAllowedDomains for all non-default COS's. So each time you redeploy the Zimlet you have to go and make that manual change. This is why I was constantly getting 403's, my manual settings kept getting wiped without my knowing it.

If it can automatically wipe my manual settings, it would be nice if it could automatically apply the supplied config settings I want to begin with so I don't need to do it manually I suspect this may also be why I couldn't access the global settings from within the js code, the config_template is probably not accessible from non-default COS's. Time to test that theory now.

Cheers,

RioGD

Please let us know, that's a interesting tidbit.