Added: lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.1193910786809.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.1193910786809.bak?rev=591298&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.1193910786809.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.1193910786809.bak Fri Nov 2 03:57:25 2007
@@ -0,0 +1,252 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 1999-2004 The Apache Software Foundation
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!-- $Id: index.xml 55543 2004-10-26 00:14:59Z gregor $ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+
+<document>
+ <header>
+ <title>Part 5: Custom Navigation in Lenya</title>
+ </header>
+ <body>
+ <p>OK, so you have the basics: you know how to install Lenya, you understand it's
+ approach to content management, you understand the pipeline bit, and you know
+ how to edit existing documents. Through playing around, you probably now know
+ how to make new pages, and create the content hierarchy for your site. Now the
+ question becomes, how do we customize the navigation to be marked up the way you
+ want.</p>
+
+ <section id="customizing_lenya_navigation_items">
+<title>Customizing Lenya
+ navigation items</title>
+
+ <p>In order to understand customizing navigation items in Lenya, you'll need to
+ understand where that's possible. In the default publication's root
+ directory, you'll see a directory called 'lenya'. It's here where you can
+ add folders and files that override the global defaults set aside for all of
+ Lenya.</p>
+
+ <p>One of the directories is 'navigation'. In there, you'll most likely see a
+ file called tabs.xsl. This is a customized version of the tabs just for the
+ default publication. But you can do others. Here's the list of the file names
+ you can add in the 'navigation' folder that will override the global
+ files:</p>
+
+ <table>
+ <tr>
+ <td colspan="1" rowspan="1">breadcrumb.xsl</td>
+ <td colspan="1" rowspan="1">The breadcrumb trails at the top of the page
+ (e.g. Home > Products > Furniture)</td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">menu.xsl</td>
+ <td colspan="1" rowspan="1">The menu at the left of the pages (in the
+ default publication, for example)</td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">tabs.xsl</td>
+ <td colspan="1" rowspan="1">The tabs at the top of the page (in the
+ default publication, they are the highest levels of nav on the
+ site)</td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">search.xsl</td>
+ <td colspan="1" rowspan="1">The search box on the site</td>
+ </tr>
+ </table>
+
+ <p>There are others, but these will do for now. You can check out what the
+ originals are in
+ /usr/local/tomcat/webapps/lenya/lenya/xslt/navigation/. It
+ requires some understanding XSLT, which is again beyond the scope of this
+ article.
+ <a href="http://www.w3schools.com/xsl/default.asp">W3Schools</a>
+ has a nice place to learn XSLT quickly.</p>
+
+ <p>We're going to take a look at the sitetree structure to find out what you're
+ capable of knowing about an item in the navigation of the site, then do a quick
+ example of how to create your own menu.</p>
+
+ </section>
+<section id="understanding_the_site_tree">
+<title>Understanding
+ the site tree</title>
+
+ <p>The site tree is the place where all the "nodes", or pages in your publication are
+ stored, preserving the hierarchy. The XML file can be found by going to the
+ content/authoring/ directory in the default publication and viewing the
+ sitetree.xml file. Let's take a look at a chunk:</p>
+
+ <source xml:space="preserve">
+ <site>
+ <node id="index">
+ <label xml:lang="en">Home</label>
+ <label xml:lang="de">Home</label>
+ </node>
+
+ <node id="tutorial">
+ <label xml:lang="en">Tutorial</label>
+ <label xml:lang="de">Tutorial</label>
+
+ <node id="new_doctype">
+ <label xml:lang="en">Create new doctype</label>
+ </node>
+ </node>
+ </site>
+ </source>
+
+ <p>The above tells us that each page is characterized by a <node> tag. Each
+ <node> tag has an "id" attribute, which is the name of the document. So, if
+ this publication's address were http://www.someplace.com/, then the ID for
+ the second node would make the address to page
+ http://www.someplace.com/tutorial.html.</p>
+
+ <p>Each node has an inner element called <label>. The label tag's contents are
+ the navigation title for the page. It's the link to the page that you see in menu of
+ the site. The xml:lang attribute signifies the language for this label, and as
+ you can see, this site has multiple supported languages: "en" for English, and
+ "de" for German.</p>
+
+ <p>Nodes can be inside other nodes. In the example above, the "new_doctype" node is
+ inside the "tutorial" node. This means that the "tutorial" page is a parent of the
+ "new_doctype" page, so they fall underneath each other like so:</p>
+
+ <source xml:space="preserve">
+ 1. Home
+ 2. Tutorial
+ a. Create new doctype
+ </source>
+
+ <p>Order is also important - the order of the nodes in the sitetree file is the order in
+ which the pages are displayed in the hierarchy of the site.</p>
+
+ </section>
+<section id="the_nav_namespace">
+<title>The nav:
+ namespace</title>
+
+ <p>An XML namespace was created for users to grab these nodes with the appropriate
+ information. So, for example, you can reference a node in your XSL using
+ nav:node. Once you reference the node, you can reference it's label too:
+ nav:label. There's some other items you can reference when you are pointing at a
+ specific node:</p>
+
+ <table>
+ <tr>
+ <td colspan="1" rowspan="1">@href</td>
+ <td colspan="1" rowspan="1">The location of the page relative to where you
+ are currently in the site</td>
+ </tr>
+
+ <tr>
+ <td colspan="1" rowspan="1">@current</td>
+ <td colspan="1" rowspan="1">A true or false value is possible to determine
+ whether or not the page you are on is the node you are referencing</td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">@visibleinnav</td>
+ <td colspan="1" rowspan="1">Another true/false value given if the page had
+ been labeled as visible in the navigation</td>
+
+ </tr>
+ </table>
+
+ <p>Hiding navigation items can be helpful for situations like form
+ submission/confirmation pages. You don't want the user to go to that page right
+ away from within the site's menu, so you hide it, letting the programming of the
+ form's input redirect the user to that page instead. Other examples abound.</p>
+
+ </section>
+<section id="Using_your_new-found_knowledge">
+<title>Using your
+ new-found knowledge</title>
+
+ <p>Let's try putting together a simple menu.xsl file that creates our own simple
+ markup. The contents are below:</p>
+
+ <source xml:space="preserve">
+ <?xml version="1.0" encoding="UTF-8" ?>
+
+ <xsl:stylesheet version="1.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:nav="http://apache.org/cocoon/lenya/navigation/1.0"
+ xmlns="http://www.w3.org/1999/xhtml"
+ exclude-result-prefixes="nav">
+
+ <xsl:template match="nav:site">
+
+ <ul>
+
+ <!-- loop through all top-level items and return as list items -->
+ <xsl:for-each select="/*/nav:node[@visibleinnav = 'true']">
+ <xsl:when test="@current = 'true'">
+ <li class="current"><a href="{@href}"><xsl:apply-templates select="nav:label"/></a></li>
+ </xsl:when>
+ <xsl:otherwise>
+ <li><a href="{@href}"><xsl:apply-templates select="nav:label"/></a></li>
+ </xsl:otherwise>
+ </xsl:for-each>
+
+ </ul>
+ </xsl:template>
+
+ <xsl:template match="nav:label">
+ <xsl:value-of select="."/>
+ </xsl:template>
+
+ </xsl:stylesheet>
+ </source>
+
+ <p>OK, so let's dissect this one. You always start with your XML prologue and
+ stylesheet tags (notice how the root stylesheet tag references the nav
+ namespace?). Then, one template is created to match the <site> tag -
+ that's the root tag that wraps around all the <node> tags in our
+ sitetree.xml file.</p>
+
+ <p>We open up the unordered list, and then we'll just loop through the top-level
+ navigation items on the site. The '/*/nav:node' part of the for-each loop steps
+ down into the site tag that you just matched (/*), and then through the nodes
+ underneath the site tag (/nav:node). Note that this is only the top level nodes,
+ not all the parents and children! Read up on
+ <a href="http://www.w3schools.com/xsl/default.asp">XSLT</a> and
+ <a href="http://www.w3schools.com/xpath/default.asp">XPath</a> to
+ better understand how this notation works.</p>
+
+ <p>For each top-level item, we test to see that node happens to be the page we are
+ looking at right now (@current = 'true'). If it is, then we open up our list tag and
+ assign it the class of "current". Your CSS can then be created to give some special
+ styling to that list item.</p>
+
+ <p>Once the list item is created, we need the link. The address for the link tag is
+ gathered from our handy @href. The text for the link will be the label of the node.
+ So, we call out another template shown at the bottom of our example menu.xsl file
+ where it basically just grabs the value of the contents inside the <label>
+ tags in the sitetree.xml file. We close the the link and the list items.</p>
+
+ <p>Of course, if this isn't the page we are on, then we do the same thing but don't add in
+ our special class. Simple, no?</p>
+
+ </section>
+<section id="give_it_a_try">
+<title>Give it a try</title>
+
+ <p>You now pretty much have the basics for putting together your own custom
+ navigation. There are those that feel our methods for generating the menus are
+ incorrect and that we should grab the nodes that we need in one fell swoop instead of
+ looping through each one, but this was the only method we could find where wewould
+ achieve the coding standards we wanted. Go experiment and have fun!</p>
+ </section>
+ </body>
+</document>
Modified: lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.meta
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.meta?rev=591298&r1=591297&r2=591298&view=diff
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.meta (original)
+++ lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.meta Fri Nov 2 03:57:25 2007
@@ -1,11 +1,16 @@
<?xml version="1.0" encoding="UTF-8"?>
<metadata xmlns="http://apache.org/lenya/metadata/1.0">
-<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
-<element key="mimeType">
-<value>application/xml</value>
+<element-set namespace="http://purl.org/dc/elements/1.1/">
+<element key="title">
+<value>5. Custom Navigation in Lenya</value>
</element>
+</element-set>
+<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
<element key="extension">
<value>xml</value>
+</element>
+<element key="mimeType">
+<value>application/xml</value>
</element>
<element key="resourceType">
<value>forrestDocument20</value>
Added: lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.meta.1193910786809.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.meta.1193910786809.bak?rev=591298&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.meta.1193910786809.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.meta.1193910786809.bak Fri Nov 2 03:57:25 2007
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<metadata xmlns="http://apache.org/lenya/metadata/1.0">
+<element-set namespace="http://purl.org/dc/elements/1.1/">
+<element key="title">
+<value>5. Custom Navigation in Lenya</value>
+</element>
+</element-set>
+<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
+<element key="extension">
+<value>xml</value>
+</element>
+<element key="mimeType">
+<value>application/xml</value>
+</element>
+<element key="resourceType">
+<value>forrestDocument20</value>
+</element>
+<element key="contentType">
+<value>xml</value>
+</element>
+</element-set>
+</metadata>
Modified: lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.rcml
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.rcml?rev=591298&r1=591297&r2=591298&view=diff
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.rcml (original)
+++ lenya/sandbox/pubs/docu/content/authoring/fddd7000-8730-11dc-ae46-9e7b5d14892d/en.rcml Fri Nov 2 03:57:25 2007
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<XPSRevisionControl xmlns="">
+<CheckIn backup="true" identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910786809" version="2"/>
+<CheckOut identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910770970"/>
<CheckIn backup="true" identity="lenya" session="60798970-8730-11dc-ae46-9e7b5d14892d" time="1193781622759" version="1"/>
<CheckOut identity="lenya" session="60798970-8730-11dc-ae46-9e7b5d14892d" time="1193781611937"/>
</XPSRevisionControl>
Added: lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.1193910798186.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.1193910798186.bak?rev=591298&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.1193910798186.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.1193910798186.bak Fri Nov 2 03:57:25 2007
@@ -0,0 +1,222 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 1999-2004 The Apache Software Foundation
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!-- $Id: index.xml 55543 2004-10-26 00:14:59Z gregor $ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+
+<document>
+ <header>
+ <title>Part 6a: mod_proxy and Lenya</title>
+ </header>
+ <body>
+ <p>We had mentioned that we were going to do articles on usecases and doctypes, but as we were
+ reconfiguring the newest version of Lenya (1.2.4 as of this writing) to be
+ installed under the ROOT context of Tomcat, we were again interested in going back
+ and fixing up our mod_proxy configurations so that the following would
+ happen:</p>
+
+ <ul>
+ <li>You can access the authoring environment with
+ http://lenya.client.com/</li>
+ <li>Any login requests to and subsequent usages of the authoring environment
+ are redirected to SSL for better security (no real certificate needed,
+ since just using it on inside)</li>
+ <li>Each publication is a directory under one virtualhost for
+ http://www.client.com/, unless a new domain name or sub-domain name was
+ needed, like http://publication.client.com/, where a separate
+ virtualhost would be created pointing to that one publication</li>
+ <li>A need for SSL pages on http://www.client.com/ (like form
+ submissions)</li>
+ </ul>
+
+ <p>It seemed like a lot to ask for, and we wasn't sure how to go about getting it done.
+ Lucky for us (or so we thought), Lenya's documentation has a
+ <a href="http://wiki.apache.org/lenya/HowToModProxy">page on
+ mod_proxy</a> for a very similar configuration. As always, however,
+ making sense of the documentation was harder than the actual configuration.
+ Here's our attempt at explaining just how to get the above setup working.</p>
+
+ <section id="getting_lenya_installed_under_the_ROOT_context">
+<title>
+ Getting Lenya installed under the ROOT context</title>
+
+ <p>So, we were trying to make things a little cleaner for ourself and having Lenya be
+ the only web application installed under Tomcat. To do this, you'll have to
+ change a couple things in your local.build.properies file before building
+ Lenya (see
+ <a href="installing_lenya.html"> installing Lenya</a> for more
+ information):</p>
+
+ <ol>
+ <li>Change the container from Jetty to Tomcat (new to
+ 1.2.4)
+ #web.app.server=Jettyweb.app.server=Tomcat</li>
+ <li>Change the tomcat.webapps.dir line to the
+ following:tomcat.webapps.dir=${tomcat.home.dir}/webapps/ROOT</li>
+ <li>Change the tomcat.cache.dir line to the
+ following:tomcat.cache.dir=${tomcat.home.dir}/work/Catalina/localhost</li>
+ </ol>
+
+ <p>While the last line may seem strange, our thinking here was that since we are only
+ using Tomcat for Lenya, if we ever reset Lenya, then we'll just clean out the
+ whole work directory before starting Tomcat again.</p>
+
+ <p>Then install as always using ./build.sh. You'll have a shiny new
+ installation under the ROOT context, where you can now access Lenya with
+ http://lenya.client.com:8080/ (notice there's no 'lenya' at the end of
+ the URL now).</p>
+
+ </section>
+<section id="a_caveat_on_SSL">
+<title>A caveat on SSL</title>
+
+ <p>Yes, we know, there's always a caveat. Well, one thing the mod_proxy document
+ doesn't mention is that you can't have two different domains or sub-domains with
+ SSL ports opened on the same Apache instance and using the same IP address. For
+ example, if we want to host http://lenya.client.com/ and
+ http://www.client.com/ on the same Apache instance and they both have the same
+ IP address (this is Name-based Virtual Hosting in Apache), you would think you
+ could do this:</p>
+
+ <source xml:space="preserve">
+ NameVirtualHost 192.168.1.100:80
+
+ <VirtualHost 192.168.1.100:80>
+ ServerName lenya.client.com
+ # rest of configuration goes here
+ </VirtualHost>
+
+ <VirtualHost 192.168.1.100:443>
+ ServerName lenya.client.com
+ # rest of configuration goes here
+ </VirtualHost>
+
+ <VirtualHost 192.168.1.100:80>
+ ServerName www.client.com
+ # rest of configuration goes here
+ </VirtualHost>
+
+ <VirtualHost 192.168.1.100:443>
+ ServerName www.client.com
+ # rest of configuration goes here
+ </VirtualHost>
+ </source>
+
+ <p>But in fact, you can't. The explanation for it is
+ <a href="http://httpd.apache.org/docs-2.0/ssl/ssl_faq.html#vhosts2">
+ in Apache's documentation</a>. The way around this would be to either get
+ another IP address for www.client.com, or assign another port to
+ www.client.com's SSL connection (instead of using the default 443). So, in this
+ case, we are going to be using another IP address. To be perfectly honest, we are
+ actually going to split the authoring and live servers on to two physical
+ machines, but setting it up this way on one server using one Apache instance is
+ good enough for demonstration purposes.</p>
+
+ </section>
+<section id="authoring_environment">
+<title>Authoring
+ environment</title>
+
+ <p>So, for this first part, we want to be able to go to http://lenya.client.com/ and get
+ the first page of Lenya, where we can choose the publication we need to edit. Here's
+ what we have (it's nearly idential to the mod_proxy how-to document on Lenya's
+ website):</p>
+
+ <source xml:space="preserve">
+ NameVirtualHost 192.168.1.100:80
+
+ <VirtualHost 192.168.1.100:80>
+ ServerName lenya.client.com
+ ServerAlias lenya
+ ProxyRequests Off
+ RewriteEngine On
+ RewriteLog logs/lenya.client.com.rewrite.log
+ RewriteLogLevel 0
+ RewriteRule ^/([^/\.]+)$ $1/ [R]
+ RewriteRule ^/([^/\.]+)/$ http://lenya.client.com/$1/authoring/index.html [R,L]
+ RewriteCond %{QUERY_STRING} lenya\.usecase=login(.*)
+ RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]
+ RewriteRule ^/(.*) http://lenya.client.com:8080/$1 [P,L]
+ ProxyPassReverse / http://lenya.client.com:8080/
+ </VirtualHost>
+
+ <VirtualHost 192.168.1.100:443>
+ ServerName lenya.client.com
+ ServerAlias lenya
+ ProxyRequests Off
+ RewriteEngine On
+ RewriteLog logs/ssl.lenya.client.com.rewrite.log
+ RewriteLogLevel 0
+ RewriteRule ^/([^/\.]+)$ $1/ [R]
+ RewriteRule ^/([^/\.]+)/$ http://lenya.client.com/$1/authoring/index.html [R,L]
+ RewriteRule ^/(.*) http://%{SERVER_NAME}:8080/$1 [P,L]
+ ProxyPassReverse / http://lenya.client.com:8080/
+ </VirtualHost>
+ </source>
+
+ <p>Let's step through this quickly. We setup our name-based virtual host for the IP
+ address assigned to lenya.client.com:</p>
+
+ <source xml:space="preserve"> NameVirtualHost 192.168.1.100:80
+ </source>
+
+ <p>In the first virtual host (the non-SSL one on port 80), we give it a name of
+ lenya.client.com, keep proxy requests off (so that it's only a reverse proxy,
+ not a forwarding one), and then turn on the rewriting engine to enable to rewrite
+ URLs. We also setup a log for the rewrites, but since the log level is 0, it won't
+ actually log anything.</p>
+
+ <p>The first group of RewriteRules are for convenience's sake, really. They match
+ everything after but up to the first forward slash that doesn't have a dot in it. In
+ other words, it's trying to match a directory, like this:</p>
+ <source xml:space="preserve"> http://lenya.client.com/default
+ </source>
+
+ <p>If it matches, it resends it as
+ http://lenya.client.com/default/authoring/index.html, meaning that it
+ goes through the whole rigamarole of matching again inside the VirtualHost.
+ Well, whenever you access the authoring environment for the first time, Lenya
+ checks to see if there's a session of you being logged in. Since there probably
+ isn't, it forwards you an address where "lenya.usecase=login"
+ something-or-another is appended to it. And that's where the second group of
+ Rewrites comes in. See the RewriteCond? It checks to see if the query string of the
+ URL has that pattern. If it does, it send it off to the SSL portion (see the https?).
+ The rest of it gets sent back to the reverse proxy, where the content is grabbed
+ from port 8080 where Tomcat is installed.</p>
+
+ <p>In the VirtualHost section for SSL on lenya.client.com, it's pretty much exactly
+ the same. If you try to hit the SSL port with just a directory, like so:</p>
+
+ <source xml:space="preserve"> https://lenya.client.com/default
+
+ </source>
+
+ <p>It rewrites the URL as
+ http://lenya.client.com/default/authoring/index.html. Here, again, it
+ goes back to the first VirtualHost, and if you aren't logged in, it eventually
+ takes you back to the SSL portion of the site to login. Otherwise, it matches
+ everything and sends it through the reverse proxy on port 8080. So, once you login
+ through SSL, you stay in SSL for all your editing.</p>
+
+ </section>
+<section id="next_part">
+<title>Next part</title>
+ <p>This article turned out to be quite long, so the next time around, which should be
+ very shortly, we will post the second half on configuring the live server
+ mod_proxy config.
+ </p>
+ </section>
+ </body>
+ </document>
Modified: lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.meta
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.meta?rev=591298&r1=591297&r2=591298&view=diff
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.meta (original)
+++ lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.meta Fri Nov 2 03:57:25 2007
@@ -1,11 +1,16 @@
<?xml version="1.0" encoding="UTF-8"?>
<metadata xmlns="http://apache.org/lenya/metadata/1.0">
-<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
-<element key="mimeType">
-<value>application/xml</value>
+<element-set namespace="http://purl.org/dc/elements/1.1/">
+<element key="title">
+<value>6a. Mod Proxy and Lenya</value>
</element>
+</element-set>
+<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
<element key="extension">
<value>xml</value>
+</element>
+<element key="mimeType">
+<value>application/xml</value>
</element>
<element key="resourceType">
<value>forrestDocument20</value>
Added: lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.meta.1193910798186.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.meta.1193910798186.bak?rev=591298&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.meta.1193910798186.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.meta.1193910798186.bak Fri Nov 2 03:57:25 2007
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<metadata xmlns="http://apache.org/lenya/metadata/1.0">
+<element-set namespace="http://purl.org/dc/elements/1.1/">
+<element key="title">
+<value>6a. Mod Proxy and Lenya</value>
+</element>
+</element-set>
+<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
+<element key="extension">
+<value>xml</value>
+</element>
+<element key="mimeType">
+<value>application/xml</value>
+</element>
+<element key="resourceType">
+<value>forrestDocument20</value>
+</element>
+<element key="contentType">
+<value>xml</value>
+</element>
+</element-set>
+</metadata>
Modified: lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.rcml
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.rcml?rev=591298&r1=591297&r2=591298&view=diff
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.rcml (original)
+++ lenya/sandbox/pubs/docu/content/authoring/ff0240f0-8730-11dc-ae46-9e7b5d14892d/en.rcml Fri Nov 2 03:57:25 2007
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<XPSRevisionControl xmlns="">
+<CheckIn backup="true" identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910798186" version="2"/>
+<CheckOut identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910769340"/>
<CheckIn backup="true" identity="lenya" session="60798970-8730-11dc-ae46-9e7b5d14892d" time="1193781634049" version="1"/>
<CheckOut identity="lenya" session="60798970-8730-11dc-ae46-9e7b5d14892d" time="1193781612827"/>
</XPSRevisionControl>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.