GitLab

out included directives to prevent caching along the way. Now we look
at the protocol (http vs https) and include directives that allow
(encourage) http pages to be cached for a short time. My reasoning is
that anything we spit out via http is documentation, and can grow a
bit stale. Sure, the menu on the left is dynamic, but not so dynanic
that it can't go a little stale too for people who are not logged in.

when backing up (cause of an error that needs to be fixed) since not
all browsers handle this the same. Instead, redraw the form with all
of the original info and a list of error messages at the top.
Conceptually simple change, but it turns out to be a pain to implement
since you need to combine the form and processing code in one page
(well, its just a lot easier to do that), and then change all of the
forms to deal with a "default" value. That is, each different kind of
input tag (text, radio, select, checkbox, etc.) requires slightly
different changes to do that. Lots of forms, lots of entries on the
forms, and its a long slow tedious process. Much nicer though, although
the code is a bit harder to grok. At the same time, I added a lot more
sanity checks of the information being passed in.

The other change is to deal with how browsers handle the back button
on a form thats been properly submitted. Not all browsers use
the cache directives the same, and I was often typing back, only to
have some form get reposted. Thats a major pain in the butt. The way
to deal with that is to have the processor send out a Location header,
which modifies the browser history so that the post is no longer in
the history. You back up straight to the unposted form (if its in the
cache). I've done this to only some forms, since its a bit of a pain
to rework things so that you can jump ahead to a page that spits out
the requisite warm fuzzies for the specific operation just completed.

I've done newproject, joinproject, update user info, newimageid, and
newimaged_dz forms.

gets spit out a lot in all of the pages (http or https).
Refine fonts and little bits in the banner.

the bottom of the page need to be localized, but wasn't in the mood.

(somewhat) so that we can do submenu easily in other pages.

already 99 percent the same, so no need for a different form and a
processing page. Just add a checkbox and footnote on regular page.

experiment info page redraw every 30 seconds when the exp state is in
the activating or swapping state. Eventually will stop when the state
changes.

in. This was mostly to support the modal change in the home link, but
since people do not like that, this stuff is probably going to get
tossed at some point.

tired of clicking through to find my own info and experiments.

capability. New DB field in the users table (pswd_expires) which is a
date field that initially gets set to one year after the user account
is created. When the password is changed via the web form, it gets
bumped 1 more year into the future *unless* the current uid is
different from the target_uid (ie: you are changing a password for
someone else). In that case, the expiration is set to the current
date, which forces the target user to change his password next time he
logs in. I've changed the menu/auth code to look for password
expiration, and when expired the menu options contain just a single
option to change the password. All other https pages will fail with a
password expired message. Normal text pages will work of course.

webglimpse dir right into search.php3. Its a simple form and I wanted
it to look a little different. It also allows me to get rid of the
FollowSymlinks change I made a couple of days ago. I've added a
install section that creates a symlink to the webglimpse dir, but
thats strictly for convenience. The install target cds into that
directory and reruns the glimpse index (its very quick cause we do not
have much documentation, perhaps a second. Overall, I do not like the
webglimpse stuff, but it will do for now.

request.

that relative links work. This old way:

	<a href="docwrapper.php3?docname=tutorial/nscommands.html">

throws off relative links cause the actual file (docwrapper.php3) is
in a different dir than the file loaded. Instead, do this:

	<a href="tutorial/docwrapper.php3?docname=nscommands.html">

So loading tutorial/docwrapper.php3 sets the current directory
properly, and then loads the specified file.

off the header and footer. Add printable=1 to the 'arguments' to docwrapper.php3
to use. Also moved the menu faq.php3 link to docwrapper.php3?docname=faq.html

radio button in the new project web page so people can opt out of
having their URL listed.

instead of https. Present doc links as http all the time.  Required
lot of little changes.

proper headers. Split out some of the mail into testbed-logs,
testbed-ops, and testbed-approval. Added a library for including from
our perl scripts. Contains a couple of mail helper functions, but will
hopefully contain more as time goes by.

Fixed a bug in the web interface that was causing breakage for people
with multiple accounts. Mac and Jay have noticed this, when logging
out and trying to join or create a project under a new or different
name.

of problems.

the sbin directory to set/clear the MOTD, as well as login/nologin.

replaced by the "images" table. New os_info table is added. New web
pages to add and delete OSIDs to/from the os_info table, for use in
the NS file. tb-create-os is gone. handle_os no longer operates on the
tbcmds file, and no longer writes anything into the ir file. Moved the
setting up of os state (nodes table) from os_setup to handle_os, where
it should be. os_load and sched_reload now take a single argument, the
name of the imageid from the images table.

interface options (but leave the documentation and web page running),
simply do this in mysql:

	insert into nologins (nologins) values(1);

To turn the interface back on:

	delete from nologins;

pages, and take out the "studmuffin" check in the main menu.