Re: cookiesrc -> DEFAULT ACCEPT works, while gmail.com ACCEPT doesn't

Roger wrote:
> > On Thu, Dec 08, 2011 at 05:15:19AM +0000, corvid wrote:
> >Roger wrote:
> >> The following cookiesrc file works for GMail:
> >> 
> >> $HOME/.dillo/cookiesrc
> >> DEFAULT ACCEPT
> >> 
> >> 
> >> But this doesn't work for GMail and Google complains cookies are not enabled.
> >> 
> >> $HOME/.dillo/cookiesrc
> >> DEFAULT DENY
> >> google.com ACCEPT
> >> 
> >> 
> >> Making this even more difficult, I found killing dpid and restart dillo was not 
> >> effective, I needed to kill Xorg too to prevent loading pages from what looked 
> >> like dillo was loading from cache.
> >
> >Did you use "dpidc stop"?
> 
> well, killall dpidc and seeing no dpi* processes should do it, correct?

No.
dpidc is the control program that can tell dpid and the dpis to stop.
And "killall dpidc" isn't going to stop the cookies dpi.

> >> But after much troubleshooting for the past hour, I've determined the above 
> >> scenario consistent.  As soon as "DEFAULT DENY, google.com ACCEPT" is entered, 
> >> Google complains cookies are not enabled every time.
> >
> >How about ".google.com ACCEPT"? Or, better yet, whatever the
> >exact hostname is.
> 
> This is weird as I look at dillo's X output.
> 
> I have:
> 
> DEFAULT ACCEPT
> google.com ACCEPT
> 
> And I'm seeing behavior (output) similar to "DEFAULT DENY, google.com ACCEPT".  
> And what I see further, stuff like wikipedia.com cookie denied, and then I see 
> google.com's cookies accepted.
> 
> Seems as if DEFAULT ACCEPT with nothing following will accept any cookie from 
> any domain.  DEFAULT ACCEPT with additional domain filters will act like 
> "DEFAULT DENY, some_domain.com ACCEPT".
> 
> Have I explain this well enough?

I don't see that behaviour. It could be that you're seeing messages
where dillo discards third-party cookies (if a page requests an
ad image from a different site and the ad image comes with a cookie,
we don't want the cookie). Or maybe everything will clear up after a
good dpidc stop.

Anyway, like I was wondering before:
How about ".google.com ACCEPT"? Or, better yet, whatever the
exact hostname is.