Re: Why don't Typhoon & Firesite work together? (and webcat)

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 17900
interpreted = N
texte = Ben Wyckoff writes: > >Fokko, > I did some testing of Typhoon over the weekend, and discovered that >it does NOT register a PIXO service. This is why you are seeing the >behavior described below. > >If FireSite is set up to autoproxy an action, it will either use PIXO or >TCP/IP. The PIXO method is more efficient, and eliminates the double line >entries. TCP/IP is a fallback that has a few disadvantages: double log >entries, and problems with the client ip address. > >I will contact Pacific Coast to ask about PIXO support in Typhoon. I >suggest you do the same. WebCat does support PIXO, and they bill Typhoon as >a subset of WebCat, so maybe we can convince them to support it. > >I will also test QPQ to see why the TCP/IP autoproxy doesn't work there, >and report back later. > >- -Ben > >Fokko van Duin writes: >>Why is it that I have to choose: >> >>FireSite 2.3 (standard version) is working for all pages (including .dna), >>but I have double log entries in WebSTAR 2.1. One entry refers to the >>webserver, the other to the actual client. Furthermore [ipaddress] returns >>the address of the server. >> >>OR >> >>FireSite is not working for .dna files, but I have a normal log in W* and >>[ipaddress] returns the client's address. >> >>I need both, but it seems impossible. Any help would be very appreciated. >> >>Fokko van DuinI reported the same behavior with Webcatalog 2.1.1 and 2.1.3 plugins to both here and the Webcat list. Here was Ben's response from a couple weeks ago:>Dale, > Thanks for providing the detailed response regarding >FireSite/WebCat integration. I didn't bother copying that info here... > >You are definitely seeing TCP/IP autoproxy, and I believe you when you say >you used to have FireSite to WebCat PIXO working. We will work to figure >out why it isn't working now. > > >You said your options [for capturing correct IPADDRESS in web pages] are: > >1) Use the X-Client-IP or X-Client-Address mimeheader, which are accessible >to Webcat >2) Turn off Autoproxy for .html files so IPADDRESS works as expected >3) Wait for a fix in either Webcat or FS. > >I would suggest (1) for now, and expect (3) soon. If you do (2), there will >be some issues related to virtual domain support for old browsers, and >redirects for URLs in the WebCat pages if you are using replication. > >regards, >-BenAnd here is a response from Grant Hulbert of PCS: >>I think there is still some kind of problem here between Firesite and >>Webcatalog (if for nothing other than PIXO compatibility), but I will let >>PCS speak to that issue. > >#1 sounds like the most compatible solution, especially since it will work >with the ACGI as well. We do have PIXO ability in WebCat plugin, but I do >not know when FireSite decides to use it or not. We are seeing correct >stuff happen via PIXO and NetCloak backend, but we do not have sample cases >set up with FireSite here. >Grant Hulbert Can anyone else confirm seeing double log entries with both Firesite and Webcatalog installed with autoproxy on?Thanks,Dale ________________________ ______________________________ | Dale LaFountain | mailto:dalel@dhorse.com | | MIS Director,WebMaster | web: http://www.dhorse.com/ | | Dark Horse Comics, Inc.|Phone: 503-652-8815 x324 | \________________________|______________________________/ Associated Messages, from the most recent to the oldest:

    
Ben Wyckoff writes: > >Fokko, > I did some testing of Typhoon over the weekend, and discovered that >it does NOT register a PIXO service. This is why you are seeing the >behavior described below. > >If FireSite is set up to autoproxy an action, it will either use PIXO or >TCP/IP. The PIXO method is more efficient, and eliminates the double line >entries. TCP/IP is a fallback that has a few disadvantages: double log >entries, and problems with the client ip address. > >I will contact Pacific Coast to ask about PIXO support in Typhoon. I >suggest you do the same. WebCat does support PIXO, and they bill Typhoon as >a subset of WebCat, so maybe we can convince them to support it. > >I will also test QPQ to see why the TCP/IP autoproxy doesn't work there, >and report back later. > >- -Ben > >Fokko van Duin writes: >>Why is it that I have to choose: >> >>FireSite 2.3 (standard version) is working for all pages (including .dna), >>but I have double log entries in WebSTAR 2.1. One entry refers to the >>webserver, the other to the actual client. Furthermore [ipaddress] returns >>the address of the server. >> >>OR >> >>FireSite is not working for .dna files, but I have a normal log in W* and >>[ipaddress] returns the client's address. >> >>I need both, but it seems impossible. Any help would be very appreciated. >> >>Fokko van DuinI reported the same behavior with Webcatalog 2.1.1 and 2.1.3 plugins to both here and the Webcat list. Here was Ben's response from a couple weeks ago:>Dale, > Thanks for providing the detailed response regarding >FireSite/WebCat integration. I didn't bother copying that info here... > >You are definitely seeing TCP/IP autoproxy, and I believe you when you say >you used to have FireSite to WebCat PIXO working. We will work to figure >out why it isn't working now. > > >You said your options [for capturing correct IPADDRESS in web pages] are: > >1) Use the X-Client-IP or X-Client-Address mimeheader, which are accessible >to Webcat >2) Turn off Autoproxy for .html files so IPADDRESS works as expected >3) Wait for a fix in either Webcat or FS. > >I would suggest (1) for now, and expect (3) soon. If you do (2), there will >be some issues related to virtual domain support for old browsers, and >redirects for URLs in the WebCat pages if you are using replication. > >regards, >-BenAnd here is a response from Grant Hulbert of PCS: >>I think there is still some kind of problem here between Firesite and >>Webcatalog (if for nothing other than PIXO compatibility), but I will let >>PCS speak to that issue. > >#1 sounds like the most compatible solution, especially since it will work >with the ACGI as well. We do have PIXO ability in WebCat plugin, but I do >not know when FireSite decides to use it or not. We are seeing correct >stuff happen via PIXO and NetCloak backend, but we do not have sample cases >set up with FireSite here. >Grant Hulbert Can anyone else confirm seeing double log entries with both Firesite and Webcatalog installed with autoproxy on?Thanks,Dale ________________________ ______________________________ | Dale LaFountain | mailto:dalel@dhorse.com | | MIS Director,WebMaster | web: http://www.dhorse.com/ | | Dark Horse Comics, Inc.|Phone: 503-652-8815 x324 | \________________________|______________________________/ Dale LaFountain

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:

Summing fields (1997) Interfacing WebMerchant to www.fedex.com (1997) RE:formula.db problems (1999) Math with Time (1997) webCatalog and Stocks (1998) webcat- multiple selection in input field (1997) serial number dishing (1997) appending to my last post (1999) Cart# (1997) Database Strategy - more... (1998) Error:Too many nested [xxx] contexts (1997) WebDNA Writer Needed (1997) Country & Ship-to address & other fields ? (1997) Reverse dating (1999) WC TableGrinder (1997) Admin Edit prob. (1997) Passing variables to Realm Authentication - WebStar (1998) 2.0 Info (1997) Authenticate (1997) authenticating a second user, the sequel (1997)