[jira] [Created] (TAP5-1902) Production Mode and AJP together changes URL behavior

["Richard Frovarp (Created) (JIRA)" <ji...@apache.org>]

Production Mode and AJP together changes URL behavior
-----------------------------------------------------

                 Key: TAP5-1902
                 URL: https://issues.apache.org/jira/browse/TAP5-1902
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.3.2
            Reporter: Richard Frovarp


With the production mode set to true, and the application being proxied to via AJP, URLs become fully qualified. When production mode is turned off, but still proxied via AJP, the URLs aren't qualified. With production mode on or off, HTTP proxies or direct calls to Jetty / Tomcat result in URLs that aren't qualified. These URLs are generated by Tapestry and extend to form POST URLs.

Examples:

Production mode on, proxy to Tomcat via AJP for the project generated by the quickstart archetype:

<div class="menu">
  <ul>
    <li class="current_page_item">
      <a href="http://myhost/url-test/">Index</a>
    </li>
    <li>
      <a href="http://myhost/url-test/about">About</a>
    </li>
    <li>
      <a href="http://myhost/url-test/contact">Contact</a>
    </li>
  </ul>
</div>

Turn production mode off in Tomcat or use mvn jetty:run the same code generates this HTML:

<div class="menu">
  <ul>
    <li class="current_page_item">
      <a href="/url-test/">Index</a>
    </li>
    <li>
      <a href="/url-test/about">About</a>
    </li>
    <li>
      <a href="/url-test/contact">Contact</a>
    </li>
  </ul>
</div>



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira