本文整理匯總了PHP中flexicontent_html::get_basedomain方法的典型用法代碼示例。如果您正苦於以下問題：PHP flexicontent_html::get_basedomain方法的具體用法？PHP flexicontent_html::get_basedomain怎麽用？PHP flexicontent_html::get_basedomain使用的例子？那麽, 這裏精選的方法代碼示例或許可以為您提供幫助。您也可以進一步了解該方法所在類flexicontent_html的用法示例。
在下文中一共展示了flexicontent_html::get_basedomain方法的1個代碼示例，這些例子默認根據受歡迎程度排序。您可以為喜歡或者感覺有用的代碼點讚，您的評價將有助於係統推薦出更棒的PHP代碼示例。
示例1: is_safe_url
static function is_safe_url($url, $baseonly = false)
{
$cparams = JComponentHelper::getParams('com_flexicontent');
$allowed_redirecturls = $cparams->get('allowed_redirecturls', 'internal_base');
// Parameter does not exist YET
// prefix the URL if needed so that parse_url will work
$has_prefix = preg_match("#^http|^https|^ftp#i", $url);
$url = (!$has_prefix ? "http://" : "") . $url;
// Require baseonly internal url: (HOST only)
if ($baseonly || $allowed_redirecturls == 'internal_base') {
return flexicontent_html::get_basedomain($url) == flexicontent_html::get_basedomain(JURI::base());
} else {
// if ( $allowed_redirecturls == 'internal_full' )
return parse_url($url, PHP_URL_HOST) == parse_url(JURI::base(), PHP_URL_HOST);
}
// Allow any URL, (external too) this may be considered a vulnerability for unlogged/logged users, since
// users may be redirected to an offsite URL despite clicking an internal site URL received e.g. by an email
//else
// return true;
}