|
|
Source code |
1 2 3 4 5 |
<?xml version="1.0" encoding="utf-8"?> <cross-domain-policy xsi:noNamespaceSchemaLocation="http://www.adobe.com/xml/schemas/PolicyFile.xsd> <allow-access-from domain="null0815.com" /> <allow-access-from domain="www.null0815.com" /> </cross-domain-policy> |
|
|
Source code |
1 2 3 4 5 6 |
<security>
<crossdomainxml url="http://www.null0815.com/crossdomain.xml" />
<crossdomainxml url="http://null0815.com/crossdomain.xml" />
<allowdomain domain="www.null0815.com" />
<allowdomain domain="null0815.com" />
</security>
|
|
|
Source code |
1 2 |
RewriteCond %{HTTP_HOST} ^null0815\.com$ [NC]
RewriteRule ^(.*)$ http://www.null0815.com/$1 [L,R=301]
|
I have tested these both links and none is working:I´ve created crossdomain.xml and have put it to our root:
Why bother with the fqdn here?
<include url="http://www.null0815.com/panorama/common/skin/nullskin.xml" />
and not
<include url="../../../panorama/common/skin/nullskin.xml" />
Actually the best method is to have a correctly configured website with a .htaccess in the root
![]()
Source code
1 2RewriteCond %{HTTP_HOST} ^null0815\.com$ [NC] RewriteRule ^(.*)$ http://www.null0815.com/$1 [L,R=301]
Hi,I have tested these both links and none is working:I´ve created crossdomain.xml and have put it to our root:
http://null0815.com/crossdomain.xml
http://www.null0815.com/crossdomain.xml
btw - when the crossdomain.xml is located at the server root then any additional setting in the krpano xml shouldn't be necessary,
and one other tip - it is possible to either relative paths or also server absolute paths - just let the path start with slash '/' - then the path will start at the server root, so using the full path with the domain itself isn't necessary,
best regards,
Klaus
Quoted
as for the server absolute paths - it should look like:
<include url="/panorama/common/skin/nullskin.xml" />
instead of:
<include url="http://www.null0815.com/panorama/common/skin/nullskin.xml" />
?
Thanx!