you can configure your....
you can configure your browser such that it will not use proxy for selected sites. So, it is possible to surf external sites via proxy and download ubuntu ultimate(or anything else for that matter) from 10.10.4.1 without proxy simultaneously.
go to edit --> preferences --> Advanced --> network tab --> settings, down there is a option 'no proxy for' write 10.10.4.1 there and it wouldn't use proxy for 10.10.4.1. u can enter any other server or wesite domain too for example, u can add .ac.in which means it wouldn't use proxy for sites ending with .ac.in (ex. www.iitd.ac.in).
Exactly what Vikas said. For those who want to wait for CSC to
implement it, they can wait for it.
Meanwhile for at least Ubuntu users, you can actually make exceptions
for proxy usage on a system wide level (including synaptic) by setting
it in System > Preferences > Network Proxy Preferences (there is a tab
for "Ignored Hosts" in Ubuntu 9.04 at least; you can add something
like 10.10.0.0/16) :P
SB
My doubt is how will the server know if the user is logged in or not. Even if we close the proxy window server still processes our request until some time. Is there any session thing... And how does the proxy login page work? Is any documentation available on this topic, please guide me.
Thanks akshat...yeah I was thinking same but there are three scripts (one simple javascript in the html itself and the other one is proxy.cgi and the other is a PAC script named proxy.btech) related to all this proxy thing, and I am confused which is responsible for what, if there is any documentation anywhere available please let me know.SRAVAN
Disclaimer: The proxy system was installed in IIT after I graduated. I
haven't used it.
Didn't somebody point out in a different thread that you can still
browse the internet even after you close the tab where you typed in
the username/password. If that's the case, then the javascript should
not be running in the background. If the guy in the other thread is
correct and the javascript code IS running in the background even
after closing the tab, then you have possibly discovered a wonderful
vulnerability in most browser implementations!
I find the above explanation a bit irregular. Again, I haven't used
the proxy system so I might be wrong. I'll give the explanation
anyways as an academic exercise. If you can use some messenger
software (say pidgin or kopete) without logging into the browser (by
only supplying the username and password) in the proxy settings, then
that means that javascript is NOT involved in authentication and
maintaining session IDs. Another tool is wget (or other command line,
non-javascript capable tools).
@Sravan, use a packet sniffer like wireshark to get an in-depth view
besides looking at the html code.
Regarding the session expiry, RFC 2616 [1] and RFC 2617 [2] indicate
that a proxy server may request for authentication or challenge the
client (browser, messenger, etc) with a give me a valid
username/password. I am assuming this happens when the session
expires. The RFCs also indicate that the client side may optionally
include authentication details even though it is not requested. The
point of saying this is that unlike the previous explan It should be
handled via the lower layers of the application ayation, instead of
the client actively sending a KEEP-ALIVE message, these features
indicate that the client is usually passive. It authenticates itself
once. If the session expires, the proxy server may challenge the
client again. Take note that this should not be happening via html or
javascript (take note of the example on Page 17 of RFC 2617). The
browser may prompt the user to provide the username and password.
Again, all my blabbering is based on my experience with using (http
type and other) proxy systems elsewhere. I guess these two RFCs should
be the authoritative answer to your question as long as the deployment
in IIT uses a standards compliant solution.
SB
[1] http://www.ietf.org/rfc/rfc2616.txt
[2] http://www.ietf.org/rfc/rfc2617.txt
Very interesting observation. Have you tried exploring if it is the
filtering is just port based or is the firewall in IIT using DPI
(looking at packet payload to identify that real FTP traffic is
transferring)?
It might be an interesting challenge to write a FTP-proxy (tunnelling
HTTP traffic over FTP) if it doesn't already exist.
SB
Very interesting observation. Have you tried exploring if it is the
filtering is just port based or is the firewall in IIT using DPI
(looking at packet payload to identify that real FTP traffic is
transferring)?
--
LUG@IITD - http://lug-iitd.org/Footer