Re: Quicken Quotes Server Error (fwd)

Hi Henrik,

I am reasonably certain it uses port 80 (or else it wouldnt reach our
proxy), and if it matched up with the deny ports ACL, wouldnt we get the
ERR_ACCESS_DENIED page served up?

This is a sample log entry of a client using Quicken (i know it doesnt say
much as is, but maybe we could compare logs and deduce the problem?):

(IP's are masked):

934194471.014 2779 123.456.789.0 TCP_MISS/200 6779 POST
http://onlsq.quicken.com/bin/qfnonl/stockqt.au.cgi -
DIRECT/onlsq.quicken.com qfn/stockqt
934196004.777 4625 123.456.789.0 TCP_MISS/200 4127 POST
http://onlsq.quicken.com/bin/qfnonl/stockqt.au.cgi -
DIRECT/onlsq.quicken.com qfn/stockqt
934196132.274 2210 123.456.789.0 TCP_MISS/200 3938 POST
http://onlsq.quicken.com/bin/qfnonl/stockqt.au.cgi -
DIRECT/onlsq.quicken.com qfn/stockqt
934196367.883 5722 123.456.789.0 TCP_MISS/200 6779 POST
http://onlsq.quicken.com/bin/qfnonl/stockqt.au.cgi -
DIRECT/onlsq.quicken.com qfn/stockqt

Is qfn/stockqt a mime type set by Quicken itself? A quick scan through
/usr/local/squid/etc/mime.conf didnt turn up a match so i assume it's from
Quicken's side?

I am wondering if some form of packet dump, or trapping the request somehow
would aid in resolving the problem, however i do not have Quicken at my
disposal to test with :(

Regards,

Chris.

At 07:38 PM 6/7/99 +0000, you wrote:

>To do anything we need to know what kind of request Quicken 98 does, and
>in what way it is not supported by Squid.
>
>First thing which springs to mind is if it uses a non-standard port
>blocked by the Safe_ports ACL check?
>
>Check your access.log and cache.log for any hints on what the request
>is.
>
>--
>Henrik Nordstrom
>Spare time Squid hacker
>
>Brian wrote:
>>
>> Does anyone know anything about this, a fix maybe?

-
=====================================================================
Chris Keladis
System Administrator

TPG Internet Pty. Ltd.
=====================================================================
Received on Wed Aug 11 1999 - 21:29:52 MDT