Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
A cookie is a cookie. it comes from the server in an http header, it's written to disk by the browser, and then sent to the server on demand as an http header.
There are two headers, Set-Cookie and Cookie, that are related to cookies. The Set-Cookie header is sent by the server in response to an HTTP request, which is used to create a cookie on the user's system. The Cookie header is included by the client application with an HTTP request sent to a server, if there is a cookie that has a matching domain and path.
There are two headers, Set-Cookie and Cookie, that are related to cookies. The Set-Cookie header is sent by the server in response to an HTTP request, which is used to create a cookie on the user's system. The Cookie header is included by the client application with an HTTP request sent to a server, if there is a cookie that has a matching domain and path.
I still don't know what happens with the header cookie (request) if the client is browsing over the proxy?
my squid 3.0 PRE5 was setuped with default settings.
well nothing happens.. it just passes through unless your proxy is deliberatley meddling with it, in which case it's whatever your proxy of choice has been told to do with it. Why are you asking this? Is there an actual problem you can let us in on??
well nothing happens.. it just passes through unless your proxy is deliberatley meddling with it, in which case it's whatever your proxy of choice has been told to do with it. Why are you asking this? Is there an actual problem you can let us in on??
yep, there is a problem with dynamic .asp pages.
users browsing over the proxy getting this message:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.