Re: RePost: NAT and the CART
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 24058
interpreted = N
texte = >>Webcat has no role whatsoever in determining where to >>send the results it creates. All it does is hand over its rendered pages >>to the web server. The web server is the component that sends the data >>back to the same *ip address* that requested the file ... >> >>And that's where your problem is. Web servers are based on the premise >>that each computer has its own unique ip address when it's on the net -- >>in other words, each ip addresses is uniquely assigned to ONE COMPUTER -- >>not to several computers that happen to be sharing the same ip address on >>a LAN. > >This is, fortunately, simply not true. A webserver differs visitors in many more ways than just the IP address.You're right Christer, a web server doesn't create connections anyways, so it doesn't care what the ip address is. The browser creates the connection and the server simply uses it to deliver its files to the proper computer ...>You can try it out for yourself. Fire up two different browsers on your own computer and browse your store - you won't get the same cart and your two shopping baskets won't be mixed.Yes, when a browser opens a connection, the files are served only to that browser because it's the one with the open connection ...>To answer the original question: the problem is that more than one visitor is using the same [cart]. Therefore the solution is to track down where and how they are assigned the same [cart]. The most possible cause is (as suggested by someone else here) that these visitors are coming from a link with a defined cart value.Yes, that's probably it ...>The second cause could be that they are surfing through a badly configured proxy server. There are several problems in this area, and several (partial) solutions.Sincerely, Kenneth Grome WebDNA Consultant
Associated Messages, from the most recent to the oldest:
>>Webcat has no role whatsoever in determining where to >>send the results it creates. All it does is hand over its rendered pages >>to the web server. The web server is the component that sends the data >>back to the same *ip address* that requested the file ... >> >>And that's where your problem is. Web servers are based on the premise >>that each computer has its own unique ip address when it's on the net -- >>in other words, each ip addresses is uniquely assigned to ONE COMPUTER -- >>not to several computers that happen to be sharing the same ip address on >>a LAN. > >This is, fortunately, simply not true. A webserver differs visitors in many more ways than just the IP address.You're right Christer, a web server doesn't create connections anyways, so it doesn't care what the ip address is. The browser creates the connection and the server simply uses it to deliver its files to the proper computer ...>You can try it out for yourself. Fire up two different browsers on your own computer and browse your store - you won't get the same cart and your two shopping baskets won't be mixed.Yes, when a browser opens a connection, the files are served only to that browser because it's the one with the open connection ...>To answer the original question: the problem is that more than one visitor is using the same
[cart]. Therefore the solution is to track down where and how they are assigned the same
[cart]. The most possible cause is (as suggested by someone else here) that these visitors are coming from a link with a defined cart value.Yes, that's probably it ...>The second cause could be that they are surfing through a badly configured proxy server. There are several problems in this area, and several (partial) solutions.Sincerely, Kenneth Grome WebDNA Consultant
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Still Stumped on ShowNext...HELP! (1997)
Nested tags count question (1997)
problems with 2 tags (1997)
Heads up, cookies *may* be outlawed in Europe (2001)
Mac: [ListFiles] bug alert (1997)
pop up menu's (1998)
RE: Formulas.db + Users.db (1997)
urls (2005)
FEA REQ: One .hdr, multiple .db's (2003)
Cancel Subscription (1996)
Date Range Issue (2006)
Using Plug-In while running 1.6.1 (1997)
Emailer.Out (1998)
database visibility (2000)
[WebDNA] OS and version (2019)
Search in 2 or more catalogs (1997)
Another bug to squash (WebCat2b13 Mac .acgi) (1997)
eCommerce Solution (2000)
WebCat2b12 forgets serial # (1997)
Unstable on my server (2000)