View Ticket
Ticket Hash: 99d0791365daaec739c53c8b94059e280efc9628
Title: Redirect problem prevents fossil access
Status: Fixed Type: Incident
Severity: Critical Priority:
Subsystem: Resolution: Fixed
Last Modified: 2010-09-26 11:34:52
Version Found In: b48f78964e
After working on the wiki yesterday, I closed all instances of Firefox. This morning, when attempting to reach the wiki to continue work, FF said "The page isn't redirecting properly".

When I attempted retrieval from a fedora command line, these were the headers returned:

HTTP/1.1 302 Moved Temporarily
Cache-Control: no-cache, no-store
Connection: close
Date: Fri, 24 Sep 2010 13:13:57 GMT
Server: Apache/1.3.37 (Unix) AuthMySQL/2.20 mod_perl/1.30 mod_ssl/2.8.28 OpenSSL/0.9.8a
Content-Length: 77
Content-Type: text/html; charset=utf-8
Client-Date: Fri, 24 Sep 2010 13:13:57 GMT
Client-Response-Num: 1
Client-Warning: Redirect loop detected (max_redirect = 7)

fossil is accessed as /cgi-bin/f

the contents of f are:

repository: /fossil/redistream

perms are a+rw to /fossil

a new repo /fossil/bingo seems to work fine, but all work in the previous repo is unavailable.

from the command line, 'fossil wiki list -R /fossil/redistream' works.

fossil all rebuild /fossil/redistream has no effect.

anonymous claiming to be ttmrichter added on 2010-09-24 15:55:24:
I experienced this problem and reported it on the mailing list. To recover from this (albeit with some annoying reconfiguration chores afterward), perform the following steps:

  1. BACK UP YOUR CURRENT, BROKEN DATABASE! (I lost my backup and Richard was thus not able to figure out what went wrong.)
  2. fossil configuration reset all -R repository-file-name
  3. fossil ui
  4. Go through your settings and re-establish your users, access, etc.

That should get you your code again at least. It doesn't solve the problem of the actual redirect, of course.

anonymous added on 2010-09-24 16:23:10:
I created a new repo, hacked together a utility to copy wiki entries from one repo to another, viewed the new wiki, and all was well.

I then exported the settings from the old one, imported to the new one, and was able to reproduce the error. This suggests that the error is visible in the settings file, I think, although I'm not experienced enough to know what's happening under the covers to recognize it.

anonymous claiming to be ttmrichter added on 2010-09-24 16:52:54:
That's certainly promising. Can you attach the settings file here?

anonymous added on 2010-09-24 18:18:19:

drh added on 2010-09-26 11:34:52:
It is still possible to mess up the "home-page" redirect by entering invalid information in the Setup/Configuration page. But the instructions on that page have been enhanced slightly. And there is now some defense against redirect loops, even if that defense is not prefect.