Re: RePost: NAT and the CART

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 24056
interpreted = N
texte = >>So this is not a problem specific to WebCat then? > >That is correct. 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 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.>>If 300 employees of company A were shopping at amazon.com >>and company A was using NAT to connect their LAN to the internet >>using one IP address, then all 300 people would look like one visitor >>to the amazon.com server, yes. > >Yes, that is correct. All amazon.com sees or cares about is that ONE ip >address -- because that's where requests are coming from, so that's where >it delivers requested files -- to the ip address that the requests came >from. If there were only one computer using that ip address, there would >be no problem whatsoever. But apparently that's not your situation ...No, this is not correct.>>But I thought the [cart] was set upon a particular browser's first >>visit and carried along in the code from page to page. > >No, the cart has nothing to do with the browser. The cart value is set by >webcat and placed in the page when webcat renders that page, then the page >is passed to the web server, then the web server sends the page to the *ip >address* where the original request came from. But in your example there >are 300 computers sharing the same ip address, and that's where your >problems lie ...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.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. ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Ljusa Id#233#er AB S-211 37 Malmoe Fax +46 40 97 99 77 Sweden http://www.ljusaideer.se Associated Messages, from the most recent to the oldest:

    
  1. Re: RePost: NAT and the CART (Christer Olsson 1999)
  2. Re: RePost: NAT and the CART (Gil Poulsen 1999)
  3. Re: RePost: NAT and the CART (Christer Olsson 1999)
  4. Re: RePost: NAT and the CART (Mike_Davis 1999)
  5. Re: RePost: NAT and the CART (Kenneth Grome 1999)
  6. Re: RePost: NAT and the CART (Mike_Davis 1999)
  7. Re: RePost: NAT and the CART (Christer Olsson 1999)
  8. Re: RePost: NAT and the CART (Kenneth Grome 1999)
  9. Re: RePost: NAT and the CART (Mike_Davis 1999)
  10. Re: RePost: NAT and the CART (Gil Poulsen 1999)
  11. Re: RePost: NAT and the CART (Kenneth Grome 1999)
  12. Re: RePost: NAT and the CART (John Jakovich 1999)
  13. Re: RePost: NAT and the CART (Mike_Davis 1999)
  14. Re: RePost: NAT and the CART (Kenneth Grome 1999)
  15. Re: RePost: NAT and the CART (Kenneth Grome 1999)
  16. Re: RePost: NAT and the CART (Mícheál O Sé 1999)
  17. RePost: NAT and the CART (Mike_Davis 1999)
>>So this is not a problem specific to WebCat then? > >That is correct. 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 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.>>If 300 employees of company A were shopping at amazon.com >>and company A was using NAT to connect their LAN to the internet >>using one IP address, then all 300 people would look like one visitor >>to the amazon.com server, yes. > >Yes, that is correct. All amazon.com sees or cares about is that ONE ip >address -- because that's where requests are coming from, so that's where >it delivers requested files -- to the ip address that the requests came >from. If there were only one computer using that ip address, there would >be no problem whatsoever. But apparently that's not your situation ...No, this is not correct.>>But I thought the [cart] was set upon a particular browser's first >>visit and carried along in the code from page to page. > >No, the cart has nothing to do with the browser. The cart value is set by >webcat and placed in the page when webcat renders that page, then the page >is passed to the web server, then the web server sends the page to the *ip >address* where the original request came from. But in your example there >are 300 computers sharing the same ip address, and that's where your >problems lie ...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.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. ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Ljusa Id#233#er AB S-211 37 Malmoe Fax +46 40 97 99 77 Sweden http://www.ljusaideer.se Christer Olsson

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:

First postarg not taking in $Commands (1997) Setting up shop (1997) [WebDNA] Does anyone host webdna sites? (2016) [WebDNA] What does PHP(5) has, that Webdna hasn't (2009) problem: search crashes webstar (1997) BUG: Random sort is not random at all..... (2000) pictures / referrer etc. (1998) Ampersand Searching (2000) Robert Minor duplicate mail (1997) RE: [WebDNA] Help me install (WebDNA 7 fastcgi install on Lion (2012) Questions about searching (1999) OT: Unix Geek Needed (2005) RE: WebCat cannot handle compatible search parameters? (1997) problems with 2 tags (1997) Separate SSL Server (1997) webcat 4.5 (2003) Location of Browser Info.txt file (1997) Date search - yes or no (1997) [WebDNA] Internal [ipaddress] ? (2009) [WebDNA] Suggested Platform (2013)