Fawri prépare-t-il un proxy/cache ?

Bonjour, suite à cette discussion => http://www.forumdz.com/showthread.php?t=14776

J'ai décidé de lancer ce sujet et chercher ensemble si oui ou non Fawri est entrain de faire transiter les données de ses abonnés via un proxy forcé ?

Si vous êtes abonné Fawri, merci de faire ce test:

Allez sur le site http://www.lagado.com/proxy-test

Et dites-moi si vous remarquez des lignes du genre :

Via (Selon la RFC 2616), Forwarded, X-Forwarded-For ou Client-ip headers.

En fichier joint, vous trouverez un cas de passage par un proxy. Merci de poster vos captures d'écrans et vos résultats.

Salutations amicales

Voila ce que ça donne

Proxy Test

 

This request appears NOT to have come via a proxy.

 

The request appears to have originated from ip address 41.104.10x.xxx

 

 

 

The Lagado Proxy Test shows details of any proxy servers you are using. It is especially useful to expose transparent proxies. These are proxies inserted between your browser and the web, typically by your ISP, and often without you knowing.

 

Sometimes a proxy will be deliberately hidden so it won't be exposed by this test. In this case you can use the Cache Test to expose stealthed transparent proxy caches.

 

 

The Raw Details

 

Here are the raw details of the request received by this server.

 

Remote IP Address 41.104.10x.xxx

 

Request Protocol HTTP/1.1 Method GET

Request Headers User-Agent Opera/9.64 (Windows NT 5.1; U; fr) Presto/2.1.1

Host http://www.lagado.com

Accept text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1

Accept-Language fr-FR,fr;q=0.9,en;q=0.8

Accept-Charset iso-8859-1, utf-8, utf-16, *;q=0.1

Accept-Encoding deflate, gzip, x-gzip, identity, *;q=0

Referer http://www.forumdz.com/showthread.php?p=101070

Pragma no-cache

Cache-Control no-cache

Connection Keep-Alive, TE

TE deflate, gzip, chunked, identity, trailers

 

 

This Server Host http://www.lagado.com IP Address 119.31.230.68

 

Date: Tuesday 7 Jul 2009 23:08:49 GMT+1000

 

Please Note: The conclusion that the request did not come via a proxy is based on the absense of the Via, Forwarded, X-Forwarded-For and Client-ip headers. It is still possible that a proxy is handling the request without announcing itself in the recommended way. (see rfc2616 & draft-ietf-http-v10-spec-01 & Squid Configuration Guide & Squid Release Notes 1.1)

 

Update 08 Feb 2002 by Lagado: Added support for Client-ip header used by some transparent proxies. See more background.

 

Update 30 Apr 2001 by Lagado: Added Cache-Control: no-cache header to proxy-test responses. This discourages HTTP/1.1 compliant proxies from returning cached test results. Also freshened the document references.

Merci à toi me_my_self_and_i

This request appears NOT to have come via a proxy.

On click ou pour faire le toast ? x)

Proxy Test

This request appears NOT to have come via a proxy.

The request appears to have originated from ip address 41.102.*.**

This request appears NOT to have come via a proxy.

The request appears to have originated from ip address 41.103.xxx.xxx

This request appears NOT to have come via a proxy.

The request appears to have originated from ip address 41.105.xx.xxx

Proxy Test

This request appears NOT to have come via a proxy.

Fawri 512

fawri 1 mega "...The conclusion that the request did not come via a proxy ..."

pour le topic ayant engendré celui là je crois que même les clients eepad sont concernés , j'en ai vu même un de chez freebox; peut etre que le problème est dans le site en question.

Bonsoir a vous ts voici le mien

 

 

tu ne devrais pas montrer ton IP entièrement... on ne sais jamais

This request appears NOT to have come via a proxy.

The request appears to have originated from ip address

The Lagado Proxy Test shows details of any proxy servers you are using. It is especially useful to expose transparent proxies. These are proxies inserted between your browser and the web, typically by your ISP, and often without you knowing.

Sometimes a proxy will be deliberately hidden so it won't be exposed by this test. In this case you can use the Cache Test to expose stealthed transparent proxy caches.

The Raw Details

Here are the raw details of the request received by this server.

Remote IP Address 41.000.000.000

Request Protocol HTTP/1.1 Method GET

Request Headers Accept */*

Referer http://www.forumdz.com/showthread.php?p=101102#pos​t101102

Accept-Language fr

User-Agent Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; FunWebProducts; GTB6; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; AskTB5.4)

Accept-Encoding gzip, deflate

Host http://www.lagado.com

Connection Keep-Alive

This Server Host http://www.lagado.com IP Address 119.00.000.00

Date: Wednesday 8 Jul 2009 5:57:55 GMT+1000

Please Note: The conclusion that the request did not come via a proxy is based on the absense of the Via, Forwarded, X-Forwarded-For and Client-ip headers. It is still possible that a proxy is handling the request without announcing itself in the recommended way. (see rfc2616 & draft-ietf-http-v10-spec-01 & Squid Configuration Guide & Squid Release Notes 1.1)

Update 08 Feb 2002 by Lagado: Added support for Client-ip header used by some transparent proxies. See more background.

Update 30 Apr 2001 by Lagado: Added Cache-Control: no-cache header to proxy-test responses. This discourages HTTP/1.1 compliant proxies from returning cached test results. Also freshened the document references.

This request appears NOT to have come via a proxy.

The request appears to have originated from ip address 41.105.xx.xxx

Avec Fawri 256

tu ne devrais pas montrer ton IP entièrement... on ne sais jamais

This request appears NOT to have come via a proxy.

The request appears to have originated from ip address 41.105.

Voici la capture (j'ai fawri)

Ok merci à vous tous et à toutes

Vos IP ne sont pas proxisés ce qui enlève tout doute fiouu

Donc rien à signaler (RAS) dans ce topic