We need a place to house some test pages for validating TBB builds against regressions and build failures. These tests can probably be static html for now, but they should be in a dir that is accessable from a couple different vhosts, to allow us to test things like url bar isolation.
It probably is a good idea to also test IP address for isolation, but no, we also need to test the domain-based stuff, so we need a second domain pointing at the thing.
rransom: don't be a jerk. Unless you're volunteering to run these hidden services yourself and accept arbitrary files from random volunteers, you should not have closed this ticket.
If gitweb will serve raw html with the proper mime type that could work I think. Though it is currently unavailable at .net and .com.
As an aside might want to check that things like our ldap web frontend aren't vulnerable to cookie theft from other .torproject.org domains.. The blog and trac look fine, at least.
Trac: Resolution: wontfix toN/A Status: closed to reopened
phobos: Small nit: It might also be useful for http://gitweb.torproject.{is,com,net}/ to work, in case we want to test scheme changes for origin policy behavior.. Right now it "works", but it serves a weird gitweb theme directory or something instead of the gitweb root.
rransom: Why don't you want gitweb to serve HTML? No one logs into it, right?
I think I'd rather use git if at all possible, so we can more easily accept and merge people's patches and track the tests themselves. Using gitweb cuts out having to copy updates from git over to commit them in svn. More importantly, it also means user branches of the TBB tests can be directly tested from their remotes without those users needing to create their own servers.
Oh, two more thoughts: We'll of course want to test that gitweb'a apache is not misconfigured such that inline php or other server-side code/SSI is allowed in .html files. Other than that, I see no major hazards. But it's also possible I missed something because I'm biased in favor of the gitweb idea.
Before this gets closed then, I think the last step is to create the repo for it. How about torbrowser-testing.git?
rransom: Why don't you want gitweb to serve HTML? No one logs into it, right?
Gitweb is intended to not serve files as HTML, because it is sometimes used to host partially trusted or untrusted repositories.
I don't have much of a problem with gitweb.tpo being reconfigured to serve files as HTML, but at a minimum, someone would have to reconfigure it. It may even require patching Gitweb.
I think I'd rather use git if at all possible, so we can more easily accept and merge people's patches and track the tests themselves. Using gitweb cuts out having to copy updates from git over to commit them in svn.
Subversion has the advantage that anyone who can commit to a repo can automatically specify files' MIME types, without having to ask an admin to hack up Gitweb or its configuration.
More importantly, it also means user branches of the TBB tests can be directly tested from their remotes without those users needing to create their own servers.
Only if those ‘user branches’ are hosted on gitweb.tpo or another specially reconfigured Gitweb installation.
That's not exactly what I said. Here's what I said:
00:35 < weasel> mikeperry: what's the deal with 5750? still something you need?
00:37 < mikeperry> in some form, yes.. not sure if that ticket is the best or final form, though..
We definitely want some place to put the web side of our test pages... If you hate the web, there's still options for you to ignore this ticket without closing it, you know.