Hi - hear what you are saying and see what you are seeing - however I dont think you heard what I was asking - what is it actually doing when its hanging?

What do the suppliers tech sup say? See you may have
been using this for years, but the threat profile that we face changes, and we make changes to the environments around which and on which your code is stored, processed and delivered.

Its likely that the site is trying to pull in some data from somewhere that is blocked, post some data somewhere its not allowed to, contact another site, fetch some data or picture from a remote location - something like that.

We do many things that remain unsung, often spending a great deal of time trying to make it look like we sit on our hands doing nothing and service is same as normal. SO - what I am saying is let us know what the code is doing. If you dont know then ask the supliers.

If you still dont know we can try and trace it or debug it for you.

Random gut feeling says an external call is being attempted that does not appear in the egress filter (all external calls have to appear in the white list - additions are vetted).

Thanks for getting back to us, and we do believe you (even if it renders up just fine - I hear you on posting).

We now have something to be doing on this.

Regards

Link please? (As I don't think you own google.com )