F.A.Q

Yes, as well as configuring BoostEdge via the WEB interface, covering 99% of requirements. BoostEdge can also be configured via the CLI. CLI access is protected by a login and controlled by a special "Bexec" shell. For further information, please see the reference manual.

BoostEdge's transparent mode allows web servers to see Internet users' IP addresses.

No. Since the applets do not send any HTTP headers for compression, the appliance does not compress the data.

There is no limit to the number of acceleration profiles, which are defined in the HTTP/S services. Each service can use multiple optimization profiles, each with a specific role, for all or part of the web server.

Yes, if the web proxy complies with the HTTP standard and relays the negotiation of the compression between the web servers and browsers. Important note: Internet Explorer does not always provide compression with a proxy by default. It is essential to check that the "Use HTTP1.1 with proxy" box is checked in Internet Explorer's "Advanced settings".

BoostEdge does not impose any limit on the number of web servers or IP or VIP addresses targeted by the compression. BoostEdge is scaled according to the data flow.

BoostEdge can optimize any application based on HTTP. It is capable of optimizing ERP, CRM, e-commerce, extranet, internet, websites and portals. BoostEdge appliances have demonstrated 100% compatibility with and effectiveness on application servers and web applications such as IBM WebSphere, Oracle, PeopleSoft, Business Object, Siebel, BEA, SAP, Hyperion and proprietary developments in XML, ASP, JSP, CGI, PHP and more.

If this limit is reached, the overflow data are bridged and are not optimized. Data pass through the BoostEdge appliance without being compressed. BoostEdge does not block the traffic.

The default deployment mode for BoostEdge and its optimization services is transparent mode. The default parameter when creating and optimizing a data processing service is transparent mode. The interception rules must be specified in order to route the data to the correct service. For more information on interception and service optimization rules, see the operating manual.

BoostEdge handles the compression. Decompression takes place on the client side, via the browser. The browser must support HTTP 1.1 to be able to understand and decompress the data received in a compressed format.

Yes. BoostEdge can be managed remotely. You simply need to authorize port 333 on your firewall (listening port for BoostEdge).

The only known incompatibility is the difficulty in inserting BoostEdge in an HSRP flow (Cisco High Availability) in active/active mode. This problem can be overcome using a bi-card BoostEdge. Other than this, there is no reported incompatibility problems with either networks or applications.

BoostEdge is inserted non-intrusively in a live network. BoostEdge can remain switched on without compression. The flow then passes through the appliance with no compression or modification of the frames at TCP level. The BoostEdge box can even be switched off electrically. The failover card switches its internal relay, which has the advantage of ensuring the electrical continuity of the cables. It's almost as if BoostEdge had never been inserted in the network.

Yes, BoostEdge can be administered remotely in HTTPS on port 333 (this can be modified) or via SSH.