Thanks for all the friendly help I got on this issue and for the near
saintlike patience Richard showed.
The problem has been solved. I blame China. (I'm only being a little
bit facetious in this.)
Something Richard asked -- about a proxy that filters anything with
"timeline" in the URL -- got
On 24 March 2011 04:05, Joshua Paine wrote:
> On 03/23/2011 01:01 PM, Michael Richter wrote:
> > I'm not sure why the bit rot with Firefox happened
>
> Did you just upgrade? 4.0 final came out in the last couple days.
>
Nope. It's still 3.6.15 here.
> We really need that wireshark packet ca
On 24 March 2011 01:14, Richard Hipp wrote:
> Do you have some strange proxy that is rewriting URLs that contain the
> keyword "timeline" in them?
>
Not to my knowledge, no. I mean I have a proxy I use to get around the
Great Firewall, but I'm pretty sure that timeline isn't in my list of
patte
On 24 March 2011 01:17, Douglas Fitzmaurice wrote:
> Are you able to make a Wireshark capture of the traffic from one of these
> requests?
> There is a tutorial on capturing using Ubuntu here:
> http://www.howtoforge.com/network-analysis-with-wireshark-on-ubuntu-9.10
> (Apologies if you know how
On 03/23/2011 01:01 PM, Michael Richter wrote:
> I'm not sure why the bit rot with Firefox happened
Did you just upgrade? 4.0 final came out in the last couple days.
We really need that wireshark packet capture to make sense of this.
--
Joshua Paine
LetterBlock: Web applications built with joy
Are you able to make a Wireshark capture of the traffic from one of these
requests?
There is a tutorial on capturing using Ubuntu here:
http://www.howtoforge.com/network-analysis-with-wireshark-on-ubuntu-9.10
(Apologies if you know how to use it, it does start with baby steps!)
On 23 March 2011 17
Do you have some strange proxy that is rewriting URLs that contain the
keyword "timeline" in them?
Does http://server/path/test_env show anything interesting or helpful?
On Wed, Mar 23, 2011 at 1:07 PM, Michael Richter wrote:
> To clarify further, the problem doesn't VANISH if I turn on history
To clarify further, the problem doesn't VANISH if I turn on history view for
user nobody. I'm still flagged as logged out and I still can't configure
the timeline from the admin panel. I can, however, see and interact with
the timeline which allows me to use my repositories at least in the short
I've tried this (and just retried it in Firefox) and in Chrome I even took
the extreme measure of disabling all extensions and then switching to
private browsing mode. Still no dice.
On 24 March 2011 01:00, Douglas Fitzmaurice wrote:
> Does switching to Private mode on either browser have any e
And another data point. I can't see the timeline SETTINGS from the admin
panel. So I log in. I click on Admin. I click on Timeline. I'm thrown to
the login page.
On 24 March 2011 01:01, Michael Richter wrote:
> And yet more data. If I turn on history view for user nobody the problem
> vani
And yet more data. If I turn on history view for user nobody the problem
vanishes.
The problem seems to be some very bad interaction between the login
credentials and the check for those in the timeline view. I'm not sure why
the bit rot with Firefox happened, but perhaps it shows a problem in t
Does switching to Private mode on either browser have any effect?
It should be an easy way to avoid any local cookies or extensions (in
Chrome) from interfering with the process.
On 23 March 2011 16:47, Michael Richter wrote:
> And more data: It seems Firefox is just plain tainted now -- I can't
And more data: It seems Firefox is just plain tainted now -- I can't access
the timeline view on ANY fossil repository, just like the problem I had for
Chrome.
On 24 March 2011 00:45, Michael Richter wrote:
> More data on this problem. It's now happening to me on Firefox. A repo
> that was wor
More data on this problem. It's now happening to me on Firefox. A repo
that was working fine for me with Firefox for several days (but not Chrome
-- no repo ever works with Chrome) has suddenly developed the same disease
using Firefox. I'm logged in. I can see everything clearly. Except the
ti
On Mon, Mar 21, 2011 at 10:21 AM, Richard Hipp wrote:
> On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter
> wrote:
>>
>> First attempt: "relay-to" was set to www.fossil-scm.org:80, "listen" was
>> set to 8180. I access http://localhost:8180 and I get ... the SQLite home
>> page, not Fossil's. T
On 21 March 2011 23:30, Richard Hipp wrote:
>
> On Mon, Mar 21, 2011 at 11:10 AM, Michael Richter wrote:
>
>> Try running the experiment here: http://www.sqlite.org/debug1
>>>
>>
> OK, I can log in and see the timeline properly here. Are you running this
>> through CGI or is this just a fossil
[since I just subscribed, so I don't have the original email]
drh wrote:
> I'm not sure how to work around that. Anybody else have any ideas on how
to
> eavesdrop on the TCP/IP connection between the web browser and the Fossil
> web server?
How about using wireshark to capture the traffic? I u
On Mon, Mar 21, 2011 at 11:10 AM, Michael Richter wrote:
> Try running the experiment here: http://www.sqlite.org/debug1
>>
>
>
> OK, I can log in and see the timeline properly here. Are you running this
> through CGI or is this just a fossil server running straight up?
>
>
It is exactly the sam
On 21 March 2011 22:48, Richard Hipp wrote:
>
>
> On Mon, Mar 21, 2011 at 10:34 AM, Michael Richter wrote:
>
>> On 21 March 2011 22:21, Richard Hipp wrote:
>>
>>>
>>>
>>> On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter
>>> wrote:
>>>
OK, perhaps I'm being as thick as a whale omlette here
On Mon, Mar 21, 2011 at 10:34 AM, Michael Richter wrote:
> On 21 March 2011 22:21, Richard Hipp wrote:
>
>>
>>
>> On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter
>> wrote:
>>
>>> OK, perhaps I'm being as thick as a whale omlette here, but I cannot get
>>> this to work at all.
>>>
>>> First att
On 21 March 2011 22:21, Richard Hipp wrote:
>
>
> On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter wrote:
>
>> OK, perhaps I'm being as thick as a whale omlette here, but I cannot get
>> this to work at all.
>>
>> First attempt: "relay-to" was set to www.fossil-scm.org:80, "listen" was
>> set to
On Mon, Mar 21, 2011 at 3:21 PM, Richard Hipp wrote:
>
>
> On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter wrote:
>
>> OK, perhaps I'm being as thick as a whale omlette here, but I cannot get
>> this to work at all.
>>
>> First attempt: "relay-to" was set to www.fossil-scm.org:80, "listen" was
On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter wrote:
> OK, perhaps I'm being as thick as a whale omlette here, but I cannot get
> this to work at all.
>
> First attempt: "relay-to" was set to www.fossil-scm.org:80, "listen" was
> set to 8180. I access http://localhost:8180 and I get ... the S
OK, perhaps I'm being as thick as a whale omlette here, but I cannot get
this to work at all.
First attempt: "relay-to" was set to www.fossil-scm.org:80, "listen" was set
to 8180. I access http://localhost:8180 and I get ... the SQLite home page,
not Fossil's. Tinkering around with various value
Oops. I didn't see this, Richard. Sorry. I'll get this set up now and
send you the results.
Once I figure out how to get Tcl working. :)
On 17 March 2011 01:21, Richard Hipp wrote:
> On Wed, Mar 16, 2011 at 11:30 AM, Michael Richter wrote:
>
>>
>> OK, this is the sequence I've tried on my m
On Wed, Mar 16, 2011 at 11:30 AM, Michael Richter wrote:
>
> OK, this is the sequence I've tried on my main workstation (Ubuntu 10.04):
>
> 1. Delete all fossil-scm.org cookies.
> 2. Close my browser (Chrome 10.0.648.134).
> 3. Re-open my browser.
> 4. Go to fossil-scm.org.
> 5. Log in.
> 6.
On Wed, Mar 16, 2011 at 16:30, Michael Richter wrote:
>
> OK, this is the sequence I've tried on my main workstation (Ubuntu 10.04):
>
> 1. Delete all fossil-scm.org cookies.
> 2. Close my browser (Chrome 10.0.648.134).
> 3. Re-open my browser.
> 4. Go to fossil-scm.org.
> 5. Log in.
> 6. C
On 16 March 2011 23:15, Michael Richter wrote:
> On 16 March 2011 19:21, Richard Hipp wrote:
>
>>
>>
>> On Wed, Mar 16, 2011 at 1:04 AM, Michael Richter wrote:
>>
>>> The ticket
>>> http://fossil-scm.org/index.html/tktview/305143bd876f693f446f78d12dbef143c46eec58
>>> is
>>> moving into "show-st
On 16 March 2011 19:21, Richard Hipp wrote:
>
>
> On Wed, Mar 16, 2011 at 1:04 AM, Michael Richter wrote:
>
>> The ticket
>> http://fossil-scm.org/index.html/tktview/305143bd876f693f446f78d12dbef143c46eec58
>> is
>> moving into "show-stopper" territory for me. I'm trying to share a
>> repositor
On Wed, Mar 16, 2011 at 1:04 AM, Michael Richter wrote:
> The ticket
> http://fossil-scm.org/index.html/tktview/305143bd876f693f446f78d12dbef143c46eec58
> is
> moving into "show-stopper" territory for me. I'm trying to share a
> repository's code through fossil to fossil non-users. The inabilit
On Wed, Mar 16, 2011 at 1:04 AM, Michael Richter wrote:
> The
> ticket http://fossil-scm.org/index.html/tktview/305143bd876f693f446f78d12dbef143c46eec58 is
> moving into "show-stopper" territory for me. I'm trying to share a
> repository's code through fossil to fossil non-users. The inability t
Yes, this would be a serious problem for us, as well.
On Wed, Mar 16, 2011 at 1:04 AM, Michael Richter wrote:
> The
> ticket http://fossil-scm.org/index.html/tktview/305143bd876f693f446f78d12dbef143c46eec58 is
> moving into "show-stopper" territory for me. I'm trying to share a
> repository's co
The ticket
http://fossil-scm.org/index.html/tktview/305143bd876f693f446f78d12dbef143c46eec58
is
moving into "show-stopper" territory for me. I'm trying to share a
repository's code through fossil to fossil non-users. The inability to log
in in the timeline views means no ability to bundle up ZIP/
33 matches
Mail list logo
