Don't assume that users actually entered a URL to proxy in an HTTP Proxy asset. This would be reasonable.

This commit is contained in:
Colin Kuskie 2012-06-07 09:39:23 -07:00
parent 2cb7c5b85b
commit 6e8801600d
2 changed files with 5 additions and 2 deletions

View file

@ -18,6 +18,7 @@
- fixed #12364: Site export loses session info
- fixed #12345: tickets in trash still show up
- fixed #12305: dbSlave breaks WebGUI when not able to connect
- fixed: Http Proxy assets with no URL to proxy cannot be deleted.
7.10.24
- fixed #12318: asset error causes asset manager to fail

View file

@ -299,8 +299,10 @@ See WebGUI::Asset::purgeCache() for details.
sub purgeCache {
my $self = shift;
WebGUI::Cache->new($self->session,$self->get("proxiedUrl"),"URL")->delete;
WebGUI::Cache->new($self->session,$self->get("proxiedUrl"),"HEADER")->delete;
if (my $proxiedUrl = $self->get("proxiedUrl")) {
WebGUI::Cache->new($self->session,$proxiedUrl,"URL")->delete;
WebGUI::Cache->new($self->session,$proxiedUrl,"HEADER")->delete;
}
$self->SUPER::purgeCache;
}