webdav: switch hard-coded JGlobus paths to those configured

The WebDAV door may use either Jetty's built-in SSL support or
support coming from JGlobus.  If the latter is chosen then
various paths are hard-coded.

This does not respect a site's configuration and, as a specific
example, results in the system-test failing.

This patch switches the JGlobus WebDAV SSL connector to use
the configured path.

Patch: http://rb.dcache.org/r/5575/
Acked-by: Gerd Behrmann
Target: master
Request: 2.6
webadmin: make query and filter options set in browser session-specific (alarms, poolqueueplots)

module: webadmin

The alarms and pool queue plots pages were erroneously storing query settings at the server level.  These were thus unintentionally being shared across user sessions.

This patch rectifies this behavior so that user settings do not interfere with each other.

Target: master
Committed: master@21b6b73bbcb27987891715b29657687d90114766
Patch: http://rb.dcache.org/r/5577
Require-notes: yes
Require-book: no
Request: 2.6
Acked-by: Tigran

Testing Done: With two different browsers with different settings.

RELEASE NOTES

Fixes a bug in the web pages for Alarms and Pool Queue Plots where the settings selected by a user/session would become global.  The fix now isolates user/session settings from each other.
dcache: alarm command line, fix minor bug

module: dcache, alarm command line interpreter

This patch does the following:

1.  Fixes bug in add and modify whereby includeInKey was not getting updated.  It also adds "group" to the help message for the attribute (missing previously).
2.  Prints out the full definition for confirmation/review before commit in both add and modify.
3.  Allows the elimination of an attribute (XML element) via the '-' character.

Target: master
Committed: master@8b658b3caa423ecdbcbb593473e002cebe068686
Patch: http://rb.dcache.org/r/5573/
Require-notes: yes
Require-book: no
Request: 2.6
Acked-by: Tigran

Testing: Tried out various options using add, remove and modify for illegal alteration by deletion of required elements; modified includeInKey, and tried to set group (with number and without, which is an error).

RELEASE NOTES:

For those who have tried out the dcache alarm definition commands, they may have noticed that "includeInKey" could not be modified once it was defined.  This bug has been fixed.  There is also a new feature allowing the deletion of a definition element using the '-' character.  The full xml for the definition is now also displayed before asking for confirmation to write.
Merge pull request #57 from alrossi/fix/2.6/alarm_cmdline

dcache: alarm command line, fix minor bug
Merge pull request #55 from paulmillar/fix/2.6/webdav-paths

webdav: switch hard-coded JGlobus paths to those configured
Merge pull request #56 from alrossi/fix/2.6/session_alarms_qpoolplots

webadmin: make query and filter options set in browser session-specific ...
Fix dCache FTP and SRM to be standards-compliant by default

The overwriteEnabled property affects FTP and SRM doors.  The default
is currently 'false', which prevents overwriting of data if the file
already exists.

RFC 959 is quite clear:

         STORE (STOR)

            This command causes the server-DTP to accept the data
            transferred via the data connection and to store the data as
            a file at the server site.  If the file specified in the
            pathname exists at the server site, then its contents shall
            be replaced by the data being transferred.  A new file is
            created at the server site if the file specified in the
            pathname does not already exist.

Therefore, by setting overwriteEnabled to 'false', dCache is not
RFC-959 compliant.  This is our default behaviour.

Similarly, SRM protocol is also quite clear how storage elements are
expected to behave.  Setting overwriteEnabled=false breaks that
expected behaviour.

Moreover, there is no additional security from setting
overwriteEnabled=false.  The client can simply delete the data and
upload afresh.

The net result is that dCache is, by default, not standards compliant
for no direct benefit.

For the 2.2 branch, we maintain the existing default value, but
include the warning text.

FOR RELEASE NOTES:

This patch adds an explanation of the overwriteEnabled configuration option.
This controls dCache's behaviour when user attempts to overwrite an existing
file via FTP or SRM.

The default behaviour is not standards-complaint.  This patch does NOT
alter this behaviour.  Sites are invited to review their configuration.

Target: master
Request: 2.6
Request: 2.2
Patch: http://rb.dcache.org/r/5544/
Acked-by: Dmitry Litvintsev
Acked-by: Tigran Mkrtchyan
Acked-by: Gerd Behrmann
Requires-notes: yes
Requires-book: no
Merge pull request #60 from paulmillar/fix/2.6/ftp_overwrite

Fix dCache FTP and SRM to be standards-compliant by default