FAQ Category: Muse Proxy

Certain kinds of Antivirus software automatically change the extension when downloading a file with exe extension via HTTP (eg. muse-win32.exe is renamed to muse-win32.1.2D0D17.efw). You should just rename the file to muse-win32.exe and run the executable. More details about the .efw extension are available here: http://www.fileinfo.net/extension/efw

One can specify an IP address for Muse Proxy to listen on for connections. By default, Muse Proxy listens on all IP addresses, on all interfaces. This setting can be changed in the ${MUSE_HOME}/proxy/MuseProxy.xml file by specifying an IP address in the “<BINDADDRESS>” field.

For Muse Proxy service to correctly work on Windows 64-bit systems you must install Muse Proxy either using the muse-proxy-setup.jar file or the executable file (muse-proxy-win32.exe). In the latter case you must set JAVA_HOME environment variable to the location of the 64-bit Java. If no JAVA_HOME is defined and there are both 32-bit JAVA and…

The short answer is Yes, Muse Proxy support TLS 1.2. Muse Proxy runs on Java, hence it uses the Java Virtual Machine security settings, it does not rely on anything from the Operating System in this regard. Also it is not compiled with any specific SSL libraries versions like other software is. Starting with Java…

A complete set of manuals on Muse Proxy is available in your installation in the following path – $MUSE_HOME/proxy/doc, where $MUSE_HOME is the location on disk where you installed it: – Muse Proxy Install.pdf. This is the installation manual. – Muse Proxy.pdf. This is a manual with general information on Muse Proxy, describing its features….

The Muse Proxy Application UI is based on skins. If you want to customize the look and feel for a Muse Proxy Application we recommend the following approach: – copy the existing skin with a different name. The skins folder is located on disk in the following location: %MUSE_HOME%\proxy\webcontexts\Applications\ APPLICATION_ID\www\static\skins where replace the APPLICATION_ID with…

The version of muse proxy can be found via putting in the following URL in an address bar on a browser such as FireFox or Internet Explorer: http://PROXY_HOST:PROXY_PORT/ProxyInformation In the above URL, PROXY_HOST is the server that is hosting Muse Proxy. PROXY PORT is the port that is running proxy. The default port for Muse…

The Flash and Java Applets resources are binary files which cannot be processed by any re-writing proxy, including Muse Proxy. Flash and Java Applets may load in pages re-written by Muse Proxy as long as there are no absolute pathnames in URLs inside them or if there is an object parameter of the Flash or…

In Muse, there are 2 types of proxy chaining: a) “ProxyChaining” happens when the MNM chains with the proxy used for source authentication. In a Muse application where we have configured a MNM_HOST to re-write the record links and a PROXY_HOST to use for authentication we have the following scenarios: 1) If the MNM and…

They are types of rewritten links handled by the ‘Navigation Manager’ web context. A) Example of ‘Type 1’ rewritten URL: http://navigationManagerHost:navigationManagerPort/com/site/?MuseProtocol=ProtocolValue&MuseHost=some.site.com &targetSiteParameter1=targetSiteParameterValue1 … &targetSiteParameterN=targetSiteParameterValueN &MuseCookie=CookieValue&MuseReferer=RefererValue &MuseAuthorization=AuthorizationValue &MuseAuthorizationScheme=AuthorizationSchemeValue &MuseProxyHost=ProxyHostValue&MuseProxyPort=ProxyPortValue &MuseProxyPac=ProxyPacValue &MuseProxyAuthorization=ProxyAuthorizationValue &MuseProxyAuthorizationScheme=ProxyAuthorizationSchemeValue &MuseCharset=CharsetValue&MuseUID=UIDValue &MuseProxyAuthenticationToken=ProxyAuthenticationTokenValue &MuseNavigationManagerMode=NavigationManagerModeValue&MusePath=PathValue A rewritten link is of ‘Type 1’ format if it contains the Muse Navigation Manager authentication markers (MuseCookie, MuseReferer, MuseProxyHost etc….