Gudelines and restrictions

Proxy portlet output

For now the proxy portlet only supports HTML-output.

Using XHTML as output method in the XSL templates has some limitations, for example script elements will be closed.

Document type

As the proxy portlet only supports HTML output, the SiteVision page it resides on must have document type HTML to validate.

Proxied applications

The proxy portlet works with most web applications but there are some guidelines for how web applications should be implemented for best result.


The proxy portlet reads the HTML output of the web application with a HTML parser. The parser can handle many abnormalities, but not all. The web application should do its best to deliver valid output according to theXHTML 1.0 specification or the HTML 1.0 specification.Tip! Internally the proxy portlet works with XML. Best performance is achieved if the output of the proxied source (i.e. the web application) is 100% valid XHTML. The proxy portlet can in then spend less execution time fixing problems or transform HTML to XML (XHTML).


The output of the proxied source (i.e. a web application) is transformed by the proxy portlet and the end result becomes a part of a SiteVision page. Because of this it is not possible to use "frames" in web applications that should be proxied.

JavaScript and AJAX

Web applications that use JavaScript and/or AJAX technologies must be implemented in such way they can handle that data is delivered from SiteVision. This is particularly important if JavaScript code connects to the server to update the output (e.g AJAX behaviour). URL's to the server of the web application should never be "hard coded" in .js files since the proxy portlet can't rewrite the content of these.