You are here: Web Apps with Visual LANSA > 6. Constructing URLs > 6.3 How is the URL processed?

6.3 How is the URL processed?

If you want to know a bit more about what happens behind the scenes read on.

After you press enter on your URL it is inspected by the LANSA Web Plugin which uses the system and partition qualifying information to retrieve the generated HTML page, <mypage>.html, from the Application Server.

The HTML generated when you compile a Web Page is really a template, it has some substitution markers, which are used by the LANSA Web Plugin to substitute the system and partition qualifying information into its response HTML. The HTML requires these details so that additional resources, like the JavaScript, can be requested using similarly formatted URLs.

After resolving the substitution markers, the LANSA Web Plugin returns the updated HTML, including the resolved system and partition information so it can request additional resources from the Application Server. The HTML code will look something like this:

<!DOCTYPE html>

<html lang="en" style="height:100%">


      <meta charset="utf-8" />

      <meta name="mobile-web-app-capable" content="yes">

      <meta name="apple-mobile-web-app-capable" content="yes">

      <meta name="apple-touch-fullscreen" content="yes">

      <meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1">

      <meta http-equiv="X-UA-Compatible" content="IE=edge">


   <body style="height:100%; margin-left:0px;margin-right:0px;margin-top:0px;margin-bottom:0px">

      <script src="/lansa14/lansa_14_1_0_0/lansa.js"></script>




            if(!LANSA){document.write("Failed to load lansa.js");return}




      </script>      <noscript>This page requires JavaScript.</noscript>



Take notice of the following lines where the system and partition qualifying information have been added into the HTML:

<script src="/lansa14/lansa_14_1_0_0/lansa.js"></script>
LANSA.init({part:"dem",sys:"lansa14", ...

Also notice the HTML specifies the languages supported at runtime, as well as which language will be used as the default if no language parameter is supplied on the URL. The ISO Codes associated with each language are identified too.