Hi,

There is an issue while connecting via http that happened in version 2.7 (we didn't have that problem in 2.6).

Let me report the whole explanation of the IT staff (translated from spanish)

The problem comes from the way visokio 2.7 builds http request:

GET http://lacaixa1:**********@data.brandchats.com/lacaixa.iok HTTP/1.1
User-Agent: Visokio/Omniscope/2.7
Accept-Encoding: gzip, deflate
Cache-Control: no-cache
Pragma: no-cache
Host: lacaixa1:**********@data.brandchats.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Proxy-Connection: keep-alive

That request is handled by our security system and responsed by:
HTTP/1.1 400 Bad Request (Malformed HTTP request)
Pragma: no-cache
Content-Type: text/html
Cache-Control: no-cache, proxy-revalidate
Content-Length: 241
Proxy-Connection: Keep-Alive
Connection: Keep-Alive
Date: Mon, 04 Jun 2012 13:08:15 GMT

Vital Security Proxy Error

Error Occurred

---

• HTTP Error Status: 400 Bad Request
• Error Reason: Malformed HTTP request

---

Please contact your system administrator



This is because of the way Visokio sends the credentials to the host.

In version 2.6 of the client this problem was bypassed unmarking the option "requires authentication", and after the first reject:
HTTP/1.1 401 Unauthorized

The client asked for credentials and after introducing it that other request was sent:
GET http://data.brandchats.com/lacaixa.iok HTTP/1.1
User-Agent: Visokio/Omniscope/2.6 b826
Accept-Encoding: gzip, deflate
Cache-Control: no-cache
Pragma: no-cache
Host: data.brandchats.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Authorization: Basic ****************************
Proxy-Connection: keep-alive

That is the most standard request, and safest way to send credentials.

Within version 2.7 that behavior has changed, and the "workaround" described above does not work, request being reject by our security system.


Is there a way to answer that issue?

Thanks a lot,
Maxime.