Opened 14 years ago

Closed 10 years ago

#47 closed defect (fixed)

autoinstallers should support vhosts

Reported by: andersk Owned by: geofft
Priority: major Milestone:
Component: web Keywords: easy
Cc:

Description

Most of our autoinstallers, in particular Wordpress, break when accessed from a URL that they weren't originally installed at. We should fix them.

Change History (9)

comment:1 Changed 14 years ago by price

This is blocking #17, which is blocking fame, fortune, and blissful relaxation.

comment:2 Changed 14 years ago by price

By which I mean that #17 is impeding #3, which I just noticed is a ticket.

comment:3 Changed 13 years ago by price

r725 fixes this for WordPress? as far as #17 requires: the installed blog works from locker.scripts.mit.edu/addrend (the Right Thing URI) and from scripts.mit.edu/~locker/addrend (the old-style URI).

The old-style URI gives a redirect to the longer locker.scripts.mit.edu/~locker/addrend, which is ugly, but the Right Thing URI works without a redirect.

Are there any other autoinstallers known not to work out of the box at the Right Thing URIs?

comment:4 Changed 13 years ago by geofft

  • Owner set to geofft
  • Status changed from new to assigned

comment:5 Changed 12 years ago by ezyang

  • Keywords easy added

The process of testing various autoinstalls on different URLs is relatively easy to do, and would be a good introductory bug for new users.

comment:6 Changed 12 years ago by mitchb

While testing autoinstallers for good behavior wouldn't be too hard for the case of scripts/~locker/foo versus locker.scripts/foo, there are some catches here:

1) The scope of this issue has expanded some. It's no longer the case that

supporting the two types of URLs above is enough; we now also want to support arbitrary URLs that users end up with by requesting vhosts from us. It's not possible (yet... until scripts-pony happens) for someone without LDAP admin bits to reassign vhost addresses repeatedly to test that case.

2) WordPress? is known to still be a huge problem in multiple ways. [725] actually

breaks some things. Because it is not truly a URL, which is what that field is supposed to contain, it causes things like XMLRPC clients to be given an incorrect URL that doesn't work (we handled an RT ticket about this recently). And additionally, regardless of the fact that you can get at the front page of the blog from any address, and see links that take you to an uglier address, you cannot log into the admin interface of our autoinstalls at locker.scripts.mit.edu/blog/wp-admin. You get a login page that keeps returning you to it with no helpful error message if you don't instead use scripts.mit.edu/~locker/blog/wp-admin.

Many (most?) pieces of web software these days at least optionally detect and continue to use whatever URL you reached them from. I guess collecting a list of which of ours will cope with all three types of URLs might be helpful.

comment:7 Changed 12 years ago by ezyang

Agreed. Such a list will let us size up what types of changes will need to be made. It's quite likely we will end up patching Wordpress to fix this.

comment:8 Changed 12 years ago by incenate

Installed mediawiki, wordpress, joomla, e107, gallery2, phpBB, and Advanced Guest Book, and attempt each from both urls. Wordpress and Gallery2 were the two that had major problems with redirection, as logging in on the scripts.mit.edu/username address takes you to the username.scripts.mit.edu address. The others seemed to work in a logically consistent manner.

comment:9 Changed 10 years ago by adehnert

  • Resolution set to fixed
  • Status changed from assigned to closed

By and large, this works. The elephant in the room here is WordPress?, which works far from ideally, but that's being traced as #204 now.

Note: See TracTickets for help on using tickets.