archive-es.com » ES » E » EPPA.ES

Total: 100

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Apache Tomcat/7.0.22
    to the manager application is split between different users Read more Release Notes Changelog Migration Guide Security Notices Documentation Tomcat 7 0 Documentation Tomcat 7 0 Configuration Tomcat Wiki Find additional important configuration information in CATALINA HOME RUNNING txt Developers may be interested in Tomcat 7 0 Bug Database Tomcat 7 0 JavaDocs Tomcat 7 0 SVN Repository Getting Help FAQ and Mailing Lists The following mailing lists are available

    Original URL path: http://ticket.eppa.es/ (2015-09-25)
    Open archived version from archive


  • Apache Tomcat 7 (7.0.22) - Documentation Index
    a web application archive and an introduction to the web application deployment descriptor WEB INF web xml Deployer Operating the Apache Tomcat Deployer to deploy precompile and validate web applications Manager Operating the Manager web app to deploy undeploy and redeploy applications while Apache Tomcat is running Realms and Access Control Description of how to configure Realms databases of users passwords and their associated roles for use in web applications that utilize Container Managed Security Security Manager Configuring and using a Java Security Manager to support fine grained control over the behavior of your web applications JNDI Resources Configuring standard and custom resources in the JNDI naming context that is provided to each web application JDBC DataSource Configuring a JNDI DataSoure with a DB connection pool Examples for many popular databases Classloading Information about class loading in Apache Tomcat including where to place your application classes so that they are visible JSPs Information about Jasper configuration as well as the JSP compiler usage SSL Installing and configuring SSL support so that your Apache Tomcat will serve requests using the https protocol SSI Using Server Side Includes in Apache Tomcat CGI Using CGIs with Apache Tomcat Proxy Support Configuring Apache Tomcat to run behind a proxy server or a web server functioning as a proxy server MBean Descriptor Configuring MBean descriptors files for custom components Default Servlet Configuring the default servlet and customizing directory listings Apache Tomcat Clustering Enable session replication in a Apache Tomcat environment Balancer Configuring using and extending the load balancer application Connectors Connectors available in Apache Tomcat and native web server integration Monitoring and Management Enabling JMX Remote support and using tools to monitor and manage Apache Tomcat Logging Configuring logging in Apache Tomcat Apache Portable Runtime Using APR to provide superior performance scalability and better integration

    Original URL path: http://ticket.eppa.es/docs/ (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - Overview
    schemaless XML elements and attributes are case sensitive Apache Ant style variable substitution is supported a system property with the name propname may be used in a configuration file using the syntax propname All system properties are available including those set using the D syntax those automatically made available by the JVM and those configured in the CATALINA BASE conf catalina properties file The configuration element descriptions are organized into the following major categories Top Level Elements Server is the root element of the entire configuration file while Service represents a group of Connectors that is associated with an Engine Connectors Represent the interface between external clients sending requests to and receiving responses from a particular Service Containers Represent components whose function is to process incoming requests and create the corresponding responses An Engine handles all requests for a Service a Host handles all requests for a particular virtual host and a Context handles all requests for a specific web application Nested Components Represent elements that can be nested inside the element for a Container Some elements can be nested inside any Container while others can only be nested inside a Context For each element the corresponding documentation follows this

    Original URL path: http://ticket.eppa.es/docs/config/ (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 (7.0.22) - Security Considerations
    to the way some browsers handle the response from a TRACE request which exposes the browser to an XSS attack support for TRACE requests is disabled by default The maxPostSize attribute controls the maximum size of a POST request that will be parsed for parameters The parameters are cached for the duration of the request so this is limited to 2MB by default to reduce exposure to a DOS attack The maxSavePostSize attribute controls the saving of POST requests during FORM and CLIENT CERT authentication The parameters are cached for the duration of the authentication which may be many minutes so this is limited to 4KB by default to reduce exposure to a DOS attack The xpoweredBy attribute controls whether or not the X Powered By HTTP header is sent with each request If sent the value of the header contains the Servlet and JSP specification versions the full Tomcat version e g Apache Tomcat 7 0 0 the name of the JVM vendor and the version of the JVM This header is disabled by default This header can provide useful information to both legitimate clients and attackers The server attribute controls the value of the Server HTTP header The default value of this header for Tomcat 4 1 x 5 0 x 5 5 x 6 0 x and 7 0 x is Apache Coyote 1 1 This header can provide limited information to both legitimate clients and attackers The SSLEnabled scheme and secure attributes may all be independently set These are normally used when Tomcat is located behind a reverse proxy and the proxy is connecting to Tomcat via HTTP or HTTPS They allow Tomcat to see the SSL attributes of the connections between the client and the proxy rather than the proxy and Tomcat For example the client may connect to the proxy over HTTPS but the proxy connects to Tomcat using HTTP If it is necessary for Tomcat to be able to distinguish between secure and non secure connections received by a proxy the proxy must use separate connectors to pass secure and non secure requests to Tomcat If the proxy uses AJP then the SSL attributes of the client connection are passed via the AJP protocol and separate connectors are not needed The ciphers attribute controls the ciphers used for SSL connections By default the default ciphers for the JVM will be used This usually means that the weak export grade ciphers will be included in the list of available ciphers Secure environments will normally want to configure a more limited set of ciphers The tomcatAuthentication attribute is used with the AJP connectors to determine if Tomcat should authenticate the user or if authentication can be delegated to the reverse proxy that will then pass the authenticated username to Tomcat as part of the AJP protocol The allowUnsafeLegacyRenegotiation attribute provides a workaround for CVE 2009 3555 a TLS man in the middle attack This workaround applies to the BIO connector It is only necessary if

    Original URL path: http://ticket.eppa.es/docs/security-howto.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 (7.0.22) - Manager App HOW-TO
    logical opposite of the undeploy command If installation and startup is successful you will receive a response like this OK Deployed application at context path foo Otherwise the response will start with FAIL and include an error message Possible causes for problems include Application already exists at path foo The context paths for all currently running web applications must be unique Therefore you must undeploy the existing web application using this context path or choose a different context path for the new one The update parameter may be specified as a parameter on the URL with a value of true to avoid this error In that case an undeploy will be performed on an existing application before performing the deployment Encountered exception An exception was encountered trying to start the new web application Check the Tomcat logs for the details but likely explanations include problems parsing your WEB INF web xml file or missing classes encountered when initializing application event listeners and filters Deploy A New Application from a Local Path Deploy and start a new web application attached to the specified context path which must not be in use by any other web application This command is the logical opposite of the undeploy command There are a number of different ways the deploy command can be used Deploy a version of a previously deployed webapp This can be used to deploy a previous version of a web application which has been deployed using the tag attribute Note that the work directory for the Manager webapp will contain the previously deployed WARs removing it would make the deployment fail http localhost 8080 manager text deploy path footoo tag footag Deploy a Directory or WAR by URL Deploy a web application directory or war file located on the Tomcat server If no path is specified the directory name or the war file name without the war extension is used as the path The war parameter specifies a URL including the file scheme for either a directory or a web application archive WAR file The supported syntax for a URL referring to a WAR file is described on the Javadocs page for the java net JarURLConnection class Use only URLs that refer to the entire WAR file In this example the web application located in the directory path to foo on the Tomcat server is deployed as the web application context named footoo http localhost 8080 manager text deploy path footoo war file path to foo In this example the war file path to bar war on the Tomcat server is deployed as the web application context named bar Notice that there is no path parameter so the context path defaults to the name of the web application archive file without the war extension http localhost 8080 manager text deploy war jar file path to bar war Deploy a Directory or War from the Host appBase Deploy a web application directory or war file located in your Host appBase directory The directory name or the war file name without the war extension is used as the path In this example the web application located in a sub directory named foo in the Host appBase directory of the Tomcat server is deployed as the web application context named foo Notice that the context path used is the name of the web application directory http localhost 8080 manager text deploy war foo In this example the war file bar war located in your Host appBase directory on the Tomcat server is deployed as the web application context named bar http localhost 8080 manager text deploy war bar war Deploy using a Context configuration xml file If the Host deployXML flag is set to true you can deploy a web application using a Context configuration xml file and an optional war file or web application directory The context path is not used when deploying a web application using a context xml configuration file A Context configuration xml file can contain valid XML for a web application Context just as if it were configured in your Tomcat server xml configuration file Here is an example Context path foobar docBase path to application foobar Context When the optional war parameter is set to the URL for a web application war file or directory it overrides any docBase configured in the context configuration xml file Here is an example of deploying an application using a Context configuration xml file http localhost 8080 manager text deploy config file path context xml Here is an example of deploying an application using a Context configuration xml file and a web application war file located on the server http localhost 8080 manager text deploy config file path context xml war jar file path bar war Deployment Notes If the Host is configured with unpackWARs true and you deploy a war file the war will be unpacked into a directory in your Host appBase directory If the application war or directory is installed in your Host appBase directory and either the Host is configured with autoDeploy true or the Context path must match the directory name or war file name without the war extension For security when untrusted users can manage web applications the Host deployXML flag can be set to false This prevents untrusted users from deploying web applications using a configuration XML file and also prevents them from deploying application directories or war files located outside of their Host appBase Deploy Response If installation and startup is successful you will receive a response like this OK Deployed application at context path foo Otherwise the response will start with FAIL and include an error message Possible causes for problems include Application already exists at path foo The context paths for all currently running web applications must be unique Therefore you must undeploy the existing web application using this context path or choose a different context path for the new one The update parameter may be specified as a parameter on the URL with a value of true to avoid this error In that case an undeploy will be performed on an existing application before performing the deployment Document base does not exist or is not a readable directory The URL specified by the war parameter must identify a directory on this server that contains the unpacked version of a web application or the absolute URL of a web application archive WAR file that contains this application Correct the value specified by the war parameter Encountered exception An exception was encountered trying to start the new web application Check the Tomcat logs for the details but likely explanations include problems parsing your WEB INF web xml file or missing classes encountered when initializing application event listeners and filters Invalid application URL was specified The URL for the directory or web application that you specified was not valid Such URLs must start with file and URLs for a WAR file must end in war Invalid context path was specified The context path must start with a slash character To reference the ROOT web application use Context path must match the directory or WAR file name If the application war or directory is installed in your Host appBase directory and either the Host is configured with autoDeploy true the Context path must match the directory name or war file name without the war extension Only web applications in the Host web application directory can be installed If the Host deployXML flag is set to false this error will happen if an attempt is made to deploy a web application directory or war file outside of the Host appBase directory List Currently Deployed Applications http localhost 8080 manager text list List the context paths current status running or stopped and number of active sessions for all currently deployed web applications A typical response immediately after starting Tomcat might look like this OK Listed applications for virtual host localhost webdav running 0 examples running 0 manager running 0 running 0 Reload An Existing Application http localhost 8080 manager text reload path examples Signal an existing application to shut itself down and reload This can be useful when the web application context is not reloadable and you have updated classes or property files in the WEB INF classes directory or when you have added or updated jar files in the WEB INF lib directory NOTE The WEB INF web xml web application configuration file is not reread on a reload If you have made changes to your web xml file you must stop then start the web application If this command succeeds you will see a response like this OK Reloaded application at context path examples Otherwise the response will start with FAIL and include an error message Possible causes for problems include Encountered exception An exception was encountered trying to restart the web application Check the Tomcat logs for the details Invalid context path was specified The context path must start with a slash character To reference the ROOT web application use No context exists for path foo There is no deployed application on the context path that you specified No context path was specified The path parameter is required Reload not supported on WAR deployed at path foo Currently application reloading to pick up changes to the classes or web xml file is not supported when a web application is deployed directly from a WAR file It only works when the web application is deployed from an unpacked directory If you are using a WAR file you should undeploy and then deploy or deploy with the update parameter the application again to pick up your changes List OS and JVM Properties http localhost 8080 manager text serverinfo Lists information about the Tomcat version OS and JVM properties If an error occurs the response will start with FAIL and include an error message Possible causes for problems include Encountered exception An exception was encountered trying to enumerate the system properties Check the Tomcat logs for the details List Available Global JNDI Resources http localhost 8080 manager text resources type xxxxx List the global JNDI resources that are available for use in resource links for context configuration files If you specify the type request parameter the value must be the fully qualified Java class name of the resource type you are interested in for example you would specify javax sql DataSource to acquire the names of all available JDBC data sources If you do not specify the type request parameter resources of all types will be returned Depending on whether the type request parameter is specified or not the first line of a normal response will be OK Listed global resources of all types or OK Listed global resources of type xxxxx followed by one line for each resource Each line is composed of fields delimited by colon characters as follows Global Resource Name The name of this global JNDI resource which would be used in the global attribute of a ResourceLink element Global Resource Type The fully qualified Java class name of this global JNDI resource If an error occurs the response will start with FAIL and include an error message Possible causes for problems include Encountered exception An exception was encountered trying to enumerate the global JNDI resources Check the Tomcat logs for the details No global JNDI resources are available The Tomcat server you are running has been configured without global JNDI resources Session Statistics http localhost 8080 manager text sessions path examples Display the default session timeout for a web application and the number of currently active sessions that fall within ten minute ranges of their actual timeout times For example after restarting Tomcat and then executing one of the JSP samples in the examples web app you might get something like this OK Session information for application at context path examples Default maximum session inactive interval 30 minutes 30 40 minutes 1 sessions Start an Existing Application http localhost 8080 manager text start path examples Signal a stopped application to restart and make itself available again Stopping and starting is useful for example if the database required by your application becomes temporarily unavailable It is usually better to stop the web application that relies on this database rather than letting users continuously encounter database exceptions If this command succeeds you will see a response like this OK Started application at context path examples Otherwise the response will start with FAIL and include an error message Possible causes for problems include Encountered exception An exception was encountered trying to start the web application Check the Tomcat logs for the details Invalid context path was specified The context path must start with a slash character To reference the ROOT web application use No context exists for path foo There is no deployed application on the context path that you specified No context path was specified The path parameter is required Stop an Existing Application http localhost 8080 manager text stop path examples Signal an existing application to make itself unavailable but leave it deployed Any request that comes in while an application is stopped will see an HTTP error 404 and this application will show as stopped on a list applications command If this command succeeds you will see a response like this OK Stopped application at context path examples Otherwise the response will start with FAIL and include an error message Possible causes for problems include Encountered exception An exception was encountered trying to stop the web application Check the Tomcat logs for the details Invalid context path was specified The context path must start with a slash character To reference the ROOT web application use No context exists for path foo There is no deployed application on the context path that you specified No context path was specified The path parameter is required Undeploy an Existing Application http localhost 8080 manager text undeploy path examples WARNING This command will delete any web application artifacts that exist within appBase directory typically webapps for this virtual host This will delete the the application WAR if present the application directory resulting either from a deploy in unpacked form or from WAR expansion as well as the XML Context definition from CATALINA BASE conf enginename hostname directory If you simply want to take an application out of service you should use the stop command instead Signal an existing application to gracefully shut itself down and remove it from Tomcat which also makes this context path available for reuse later In addition the document root directory is removed if it exists in the appBase directory typically webapps for this virtual host This command is the logical opposite of the deploy command If this command succeeds you will see a response like this OK Undeployed application at context path examples Otherwise the response will start with FAIL and include an error message Possible causes for problems include Encountered exception An exception was encountered trying to undeploy the web application Check the Tomcat logs for the details Invalid context path was specified The context path must start with a slash character To reference the ROOT web application use No context exists for path foo There is no deployed application on the context path that you specified No context path was specified The path parameter is required Finding memory leaks http localhost 8080 manager text findleaks statusLine true false The find leaks diagnostic triggers a full garbage collection It should be used with extreme caution on production systems The find leaks diagnostic attempts to identify web applications that have caused memory leaks when they were stopped reloaded or undeployed Results should always be confirmed with a profiler The diagnostic uses additional functionality provided by the StandardHost implementation It will not work if a custom host is used that does not extend StandardHost Explicitly triggering a full garbage collection from Java code is documented to be unreliable Furthermore depending on the JVM used there are options to disable explicit GC triggering like XX DisableExplicitGC If you want to make sure that the diagnostics were successfully running a full GC you will need to check using tools like GC logging JConsole or similar If this command succeeds you will see a response like this leaking webapp If you wish to see a status line included in the response then include the statusLine query parameter in the request with a value of true Each context path for a web application that was stopped reloaded or undeployed but which classes from the previous runs are still loaded in memory thus causing a memory leak will be listed on a new line If an application has been reloaded several times it may be listed several times If the command does not succeed the response will start with FAIL and include an error message Server Status From this link you can view information about the server First you have the server and JVM version number JVM provider OS name and number followed by the architecture type Second there is several information about the memory usage of the JVM available total and max memory Then there is information about the Tomcat AJP and HTTP connectors The same information is available for both of them Threads information Max threads min and max spare threads current thread count and current thread busy Request information Max processing time and processing time request and error count bytes received and sent A table showing Stage Time Bytes Sent Bytes Receive Client VHost and Request All existing threads are listed in the table Here is the list of the possible thread stages Parse and Prepare Request The request headers are being parsed or the necessary preparation to read the request body if a transfer encoding has been specified is taking place Service The thread is processing a request and generating the response This stage follows the Parse and Prepare Request stage and precedes the Finishing stage There is always at least one thread in

    Original URL path: http://ticket.eppa.es/docs/manager-howto.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 (7.0.22) - Clustering/Session Replication HOW-TO
    attribute sessionIdAttribute you can change the request attribute name that included the old session id Default attribute name is org apache catalina cluster session JvmRouteOrignalSessionID Trick You can enable this mod jk turnover mode via JMX before you drop a node to all backup nodes Set enable true on all JvmRouteBinderValve backups disable worker at mod jk and then drop node and restart it Then enable mod jk Worker and disable JvmRouteBinderValves again This use case means that only requested session are migrated Configuration Example Cluster className org apache catalina ha tcp SimpleTcpCluster channelSendOptions 6 Manager className org apache catalina ha session BackupManager expireSessionsOnShutdown false notifyListenersOnReplication true mapSendOptions 6 Manager className org apache catalina ha session DeltaManager expireSessionsOnShutdown false notifyListenersOnReplication true Channel className org apache catalina tribes group GroupChannel Membership className org apache catalina tribes membership McastService address 228 0 0 4 port 45564 frequency 500 dropTime 3000 Receiver className org apache catalina tribes transport nio NioReceiver address auto port 5000 selectorTimeout 100 maxThreads 6 Sender className org apache catalina tribes transport ReplicationTransmitter Transport className org apache catalina tribes transport nio PooledParallelSender Sender Interceptor className org apache catalina tribes group interceptors TcpFailureDetector Interceptor className org apache catalina tribes group interceptors MessageDispatch15Interceptor Interceptor className org apache catalina tribes group interceptors ThroughputInterceptor Channel Valve className org apache catalina ha tcp ReplicationValve filter gif js jpeg jpg png htm html css txt Deployer className org apache catalina ha deploy FarmWarDeployer tempDir tmp war temp deployDir tmp war deploy watchDir tmp war listen watchEnabled false ClusterListener className org apache catalina ha session ClusterSessionListener Cluster Break it down Cluster className org apache catalina ha tcp SimpleTcpCluster channelSendOptions 6 The main element inside this element all cluster details can be configured The channelSendOptions is the flag that is attached to each message sent by the SimpleTcpCluster class or any objects that are invoking the SimpleTcpCluster send method The description of the send flags is available at our javadoc site The DeltaManager sends information using the SimpleTcpCluster send method while the backup manager sends it itself directly through the channel For more info Please visit the reference documentation Manager className org apache catalina ha session BackupManager expireSessionsOnShutdown false notifyListenersOnReplication true mapSendOptions 6 Manager className org apache catalina ha session DeltaManager expireSessionsOnShutdown false notifyListenersOnReplication true This is a template for the manager configuration that will be used if no manager is defined in the Context element In Tomcat 5 x each webapp marked distributable had to use the same manager this is no longer the case since Tomcat you can define a manager class for each webapp so that you can mix managers in your cluster Obviously the managers on one node s application has to correspond with the same manager on the same application on the other node If no manager has been specified for the webapp and the webapp is marked distributable Tomcat will take this manager configuration and create a manager instance cloning this configuration For more info Please visit the reference documentation Channel className org apache catalina tribes group GroupChannel The channel element is Tribes the group communication framework used inside Tomcat This element encapsulates everything that has to do with communication and membership logic For more info Please visit the reference documentation Membership className org apache catalina tribes membership McastService address 228 0 0 4 port 45564 frequency 500 dropTime 3000 Membership is done using multicasting Please note that Tribes also supports static memberships using the StaticMembershipInterceptor if you want to extend your membership to points beyond multicasting The address attribute is the multicast address used and the port is the multicast port These two together create the cluster separation If you want a QA cluster and a production cluster the easiest config is to have the QA cluster be on a separate multicast address port combination the the production cluster The membership component broadcasts TCP adress port of itselt to the other nodes so that communication between nodes can be done over TCP Please note that the address being broadcasted is the one of the Receiver address attribute For more info Please visit the reference documentation Receiver className org apache catalina tribes transport nio NioReceiver address auto port 5000 selectorTimeout 100 maxThreads 6 In tribes the logic of sending and receiving data has been broken into two functional components The Receiver as the name suggests is responsible for receiving messages Since the Tribes stack is thread less a popular improvement now adopted by other frameworks as well there is a thread pool in this component that has a maxThreads and minThreads setting The address attribute is the host address that will be broadcasted by the membership component to the other nodes For more info Please visit the reference documentation Sender className org apache catalina tribes transport ReplicationTransmitter Transport className org apache catalina tribes transport nio PooledParallelSender Sender The sender component as the name indicates is responsible for sending messages to other nodes The sender has a shell component the ReplicationTransmitter but the real stuff done is done in the sub component Transport Tribes support having a pool of senders so that messages can be sent in parallel and if using the NIO sender you can send messages concurrently as well Concurrently means one message to multiple senders at the same time and Parallel means multiple messages to multiple senders at the same time For more info Please visit the reference documentation Interceptor className org apache catalina tribes group interceptors TcpFailureDetector Interceptor className org apache catalina tribes group interceptors MessageDispatch15Interceptor Interceptor className org apache catalina tribes group interceptors ThroughputInterceptor Channel Tribes uses a stack to send messages through Each element in the stack is called an interceptor and works much like the valves do in the Tomcat servlet container Using interceptors logic can be broken into more managable pieces of code The interceptors configured above are TcpFailureDetector verifies crashed members through TCP if multicast packets get dropped this interceptor protects against false positives ie the node marked as crashed even though it still

    Original URL path: http://ticket.eppa.es/docs/cluster-howto.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 (7.0.22) - Tomcat Setup
    permissions see the Windows Services administration tool and its documentation Java location The installer will use the registry or the JAVA HOME environment variable to determine the base path of a Java SE 6 JRE Tray icon When Tomcat is run as a service there will not be any tray icon present when Tomcat is running Note that when choosing to run Tomcat at the end of installation the tray icon will be used even if Tomcat was installed as a service Refer to the Windows Service HOW TO for information on how to manage Tomcat as Windows NT service The installer will create shortcuts allowing starting and configuring Tomcat It is important to note that the Tomcat administration web application can only be used when Tomcat is running Unix daemon Tomcat can be run as a daemon using the jsvc tool from the commons daemon project Source tarballs for jsvc are included with the Tomcat binaries and need to be compiled Building jsvc requires a C ANSI compiler such as GCC GNU Autoconf and a JDK Before running the script the JAVA HOME environment variable should be set to the base path of the JDK Alternately when calling the configure script the path of the JDK may be specified using the with java parameter such as configure with java usr java Using the following commands should result in a compiled jsvc binary located in the CATALINA HOME bin folder This assumes that GNU TAR is used and that CATALINA HOME is an environment variable pointing to the base path of the Tomcat installation Please note that you should use the GNU make gmake instead of the native BSD make on FreeBSD systems cd CATALINA HOME bin tar xvfz commons daemon native tar gz cd commons daemon 1 0 x

    Original URL path: http://ticket.eppa.es/docs/setup.html (2015-09-25)
    Open archived version from archive

  • Application Developer's Guide (7.0.22) - Table of Contents
    covered here with links and references to other sources of information Installation Covers acquiring and installing the required software components to use Tomcat for web application development Deployment Organization Discusses the standard directory layout for a web application defined in the Servlet API Specification the Web Application Deployment Descriptor and options for integration with Tomcat in your development environment Source Organization Describes a useful approach to organizing the source code

    Original URL path: http://ticket.eppa.es/docs/appdev/ (2015-09-25)
    Open archived version from archive