If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Enjoy an ad free experience by logging in. Not a member yet? Register.

When you request a page, your browser sends lines of text called request headers (you can't see these, it's done transparently). The webserver then grabs the page (using php in the process) and then generates reply headers. Your cookies are set in the reply headers. After the reply headers comes the html.

What this means is that your cookies are only set on the client computer AFTER your page has been sent to their browser.

By default a browser will return cookies to a site if they came from that domain. That means when you make another page request, the browser will automatically send the cookies and their values back.

You can see more about this in my signature link below about headers already sent.

No business? Sheesh, if you have that attitude as a webmaster then good luck!

As for the second part, it's quite common for companies to disable JS on their browsers to stop their company networks being hit with drive by downloads.

But hey, they've got no business doing that right?

That's not my attitude, it's the people who run the website's attitude. Their site won't work without it, what are you doing on a site that isn't working. And a company can require that someone not mess with the JS settings on their company issued machines. Me, I'm just throwing out another way that the guy can solve his problem, one known to work.