• W2 Frame contents on start-up
• W3 Forms default to View-Only mode if user not logged in
• W4 Calling Forms directly - not via a Browse
• W5 I get an error when compiling my NetWebHandler procedure...
• W6 I want a menu item that links to another site
• W7 How many simultaneous connections can an EXE made with NetTalk WebServer
• W8 How many page requests can be handled
• W9 Why doesn't my Browse Filter work?
• W12 Sending a file to the browser as a Page
• W13 Client IP Address
• W16 Adding the Web Server to a Multi-DLL app
• W17 How can my User LogOut
• W18 How do I refresh the page in another Frame when this frame loads?
• W19 How do I create my own Styles?
• W20 What is the __ (double underscore) for?
• W21 How do I get additional information from a lookup?
• W22 How do I do Reports in a Web app?
• W23 Where can I host NetTalk server apps?
• W24 How can I create my own Error page?
• W25 In my FormPage, I want to call my own method to update a file, how do I prevent NetTalk from updating the tables?
• W26 How to set a value from the menu that gets passed to my product browse so I can filter that by the a product category.
• W27 I upgraded to version 4.31 (or later) and now I'm getting compile errors in my WebHandler procedure.
• W28 Error: "Subject Alternative Name Missing" or NET::ERR_CERT_COMMON_NAME_INVALID or "Your connection is not private"

Question:

I’d like one of the browses to display immediately after a successful login (as opposed to the user having to click a menu option.)  What’s the best way/place of doing that?

Each frame inside the frameset has a default URL setting. Go to your FrameSet procedure, identify which frame you want to default, and enter the URL in there. Remember you can use a procedure name as a URL.

Question:

I can see the option which requires a person to be logged in in order to see the Form. However if that fails then it goes to the Login window. I’d like it to revert to view-only mode if the person is not logged in.

p_web.GetSessionLoggedIn()=0

Example 24 contains two examples of this. One via a menu item (direct) and the other as the Save URL of a form.

The URL needs to contain 2 pieces of information. The Action to be taken, and (for some actions) an ID of the record being edited.

The action is passed as one of the following parameters;

?insert_btn=insert
?copy_btn=copy
?change_btn=change
?view_btn=view

?delete_btn=delete

p_web.AddBrowseValue (string proc, string filename, key filekey, <field1Value>, <field2Value>, <field3Value>, <field4Value>, <field5Value>)

'SomeForm?change_btn=change&_bidv_=' & p_web.AddBrowseValue('pageheadertag','mailboxes',MAI:PrimaryKey,2)

First, take the case where you’re using a Menu extension. In this case all we need to know is the correct URL, the rest is done for us.

or

MailboxesFormControl?Insert_btn=Insert&

MailboxesFormControl?Change_btn=Change&

<a href="put the url explained above here">Login</a>

Update: Putting the session Id in the URL is considered a "small" security risk. It is considered better to pass the Session ID via a cookie (which NetTalk already does). So it is not necessary, and possibly not desired, to pass the session ID in the URL.

Advanced

1. On the Form procedure options you can specify the "URL on Save" and "URL on Cancel". This is fine, as long as the Form will only be called directly (ie not from a Browse).
2. An alternative method is where you want the form to behave normally when called from a Browse, but differently when called from a direct link. To do this add a _ChainToPage_ parameter to the URL's described above. For example, if you want the frame (that the form appeared in) to return to the IndexPage, when Save (or Cancel) is clicked, then the URL would contain
   &_ChainToPage_=IndexPage
   
   For example
   
   MailboxesFormControl&MAI__MailBoxNumber=12&Change_btn=Change&_ChainToPage_=IndexPage

Syntax error : Unknown procedure label

ProcedureName(Self)

1. Make sure the Declare Globally option is switched on.
2. Make sure the Prototype for the procedure is set to (NetWebServerWorker p_web)

This is like going into a tire shop and asking the guy "If I put those tires on my car how fast will it go?" To answer that question the dealer needs to know something about your car. Putting 8 inch retreads on a Ferrari will matter. But putting 30 inch low-profiles on your Datsun isn't going to make it go any quicker.

In the same way, when considering performance, there are a number of factors that have to be taken into consideration.

• bandwidth
• complexity of the pages being served
• size of the pages being served (relates to bandwidth as well)
• speed of the database (and all that that entails)
• speed of the computer (cpu) which is doing the serving

and so on.

But what's the ballpark? Ok well on my machine (AMD 2600+) I ran various examples. On another machine on the LAN I ran a performance test utility. During the test my CPU went to 100%, which is good, it means we're testing the Server program. I tried with browse pages (16 records), Menus, Forms and so on. In all the tests I ran performance was in the 110-120 pages per second bracket.

So let's say you had 100 users, all getting a page every single second. Well it would cope with that comfortably.

This is with the class still in the beta stage, and running unoptimized code. We expect performance in the future to get even quicker than this.

If you do the filter like this :
'wmu:cust_no=loc:cust_no'
then loc:cust_no would need to be BINDed (_after_ the PUSHBIND).
 
however the filter could better be written as
 
'wmu:cust_no=' & loc:cust_no    (if loc:cust_no is a LONG)
or
'wmu:cust_no=''' & clip(loc:cust_no) & ''''   (if loc:cust_no is a STRING)
or
'UPPER(wmu:cust_no)=UPPER(''' & clip(loc:cust_no) & ''')'   (if loc:cust_no is a case insensitive STRING)

and none of these would require binding.

Question:

I have a procedure, that generates a file. I want the file to be sent to the browser. I want this file to be the "whole page" sent to the browser.

Answer:

Remember all a web server does is send files to a browser. So this is a really simple thing to accomplish. But there are some gotchas you need to consider:

• The file needs to be in a format that the Browser can display. So sending an HTM or PDF file to the browser is no problem, but sending say a TPS file to a browser isn't going to give you much joy.
• The user has to ask for the file. This is usually done via either a Link, or a Button. The URL you use would be the name of the procedure that generates the file.
• You may, or may not, want to display the file in the current browser window. If you want a new window to open remember to set the target of the URL to '_blank' .
• Remember, for security reasons the Browser cannot serve files unless they are in the Web folder (or a subfolder of Web). So your procedure needs to generate the file into the correct place.

The code you need to add is simple.

1. Firstly, you want to pass in the Web Handler to the procedure. So add
   NetWebServerWorker p_web
   as a parameter to the procedure.  If you want to call this procedure from other places in your code then you can make the parameter optional if you like. ie
   <NetWebServerWorker p_web>
2. Let the procedure generate the file as normal. Avoid displaying a window if possible (use window{prop:hide} = 1 to hide the window) and make 100% certain that no user attention is required when running the procedure. Remember this procedure will run on the Server, so the user will not see it.
3. After the file has been created, send it to the browser using the following code:
   If Not p_Web &= NULL
     p_web._Sendfile(clip(p_web.site.WebFolderPath) & '\' & filename)
   End
4. You may also want to REMOVE the file at the end of the procedure if it does not need to be stored.
    

Question:

I'm planning an app using the NetTalk web server, and I need to record the visitor's IP address.  Can you tell me where I might be able to locate the client's IP?

Answer:

The incoming IP number is stored in the header of the incoming GET or POST.
It is easily accessible from anywhere in your app (that's processing the page request)
It's stored in
 
p_web.RequestData.FromIP

Question:

Does the web server functionality work with a multi-dll app? I've given it a try, and the program always fails to initialize?

Answer:

Yes it does work, see example number 20, MultiDLL.

To use the Web Server in a Multi-DLL situation, follow these steps:

1. Open the Data DLL app. Add the NetTalk Global Extension. (Remove the Suppress NetTalk extension if it is already there.) Compile.
2. Open the App which will contain the server. Add the NetTalk Global extension, and the Activate Net Web Server Global extension.
3. Use the template utility to import the WebServer and WebHandler procedures into the App.
4. Add NetWeb procedures as normal. Compile.
5. If Step 2 was the Exe app then you're done. If not, open the Exe App. Add a call to the WebServer procedure somewhere, so you can start the web server. Compile. And Run.
   

In order to logout one of two things needs to happen.
a) If they are inactive for a certain amount of time (NetWebServer.SessionExpiryAfterHS property) then their session is deleted, and hence they are logged out. Or
b) In your code you make a call to p_web.SetSessionLoggedIn(0)

Cunningly, if you have the following parameter in your URL then a logout will be done for you
logout_btn=anything

For examples of Logout techniques see

•     Example 3

1. Uses an HTML window to confirm if the user wants to Logout. (LogoutForm procedure, note logout code embedded in this procedure).
    
2. Uses a pop-up message to confirm if the user wants to Logout. (PageHeaderTag procedure, Logout(js) menu item, the URL is
   'IndexPage?Logout_btn=yes'
   but notice the onClick code on the URL Options button
   'return chooseAction(''Do you want to Logout?'')'
   This chooseAction line is the bit that makes the popup window appear on the screen. The URL is only invoked if the user selects Yes.    Example 4
           Uses a logout link to make the logout happen
           Uses a logout URL to make the logout happen

• Example 4

Logout options are included in the MenuOnLeft procedure. Note that the two logout options here are NOT in the menu itself. You'll find them in the HTML tab under the NetWebPage Settings button.

1. The clickable link URL looks like this
   <a href="FramePage<!-- Net:s:SID -->&Logout_btn=yes" target="_top">LogOut</a>
    
2. And there is also a button, wrapped in a small <form> that looks like this
   <form action="FramePage" method="post" name="Form_frm" id="Form_frm" target="_top">
   <!-- Net:s:SessionID-->
   <input type="submit" value="Logout" name="logout_btn" class="mainbutton">
   </Form>
    

When you are sending a page to a browser you can embed JavaScript in the page.
It doesn't matter too much where the Script is, but I usually put it at the bottom of the page, after the </form> statement.
The code to for a frame to refresh looks like this

<script> top.frames.top_fram.location.reload(true) </script>

Where top_fram is the name of the frame you want to refresh.

Here's an example that conditionally loads the top frame, or the left frame, depending on the existence of a local value.

if p_web.IfExistsValue('loc:no')
  packet = clip(packet) & '<script> top.frames.top_fram.location.reload(true) </script>'
  packet = clip(packet) & '<script> top.frames.left_fram.location.reload(true) </script>'
end

The first thing you'll want to do is to create your own style file. This will allow you to make your own styles, without your styles being overwritten by the shipping NetTalk files.

1. Make a new text file in the \web\styles folder. You can call it anything you like, something like custom.css is a good name.
2. The syntax for a style is
   .rightjustify{
   text-align: right;
   }
   where the attributes for the style are inside the { } and the name is before it (prepended with a . )
   Have a look through the netweb.css file to find styles to use as starting points.
   Remember each style needs a unique name.
3. In your web server app, add the Style file to the list of styles used by the site. This is done on the webServer procedure, NetTalk Extension, Settings Tab, Styles Tab.
4. Change the item you want to use the new style.

Question:

In many of the URL's there is a double underscore. For example see question W4 above. What is this?

Answer:

Basic HTML does not allow for a colon (:) to be used in a field name. As a simple workaround NetTalk uses a double underscore in place of a colon. This is translated automatically for you where appropriate. However if you are coding a URL yourself (like the W4 example above) then you need to use a double underscore in place of a colon. For example fil:key becomes fil__key.

If you have an underscore in the name already then you'll need to add that in as well, potentially getting 3 underscores. eg fil:_key becomes fil___key.

If you have a double underscore in the name already then let me know. You're going to have a problem.

Question:

I have an Invoice line item, and I do a lookup on the product code. I'd like the Price from the products file to be entered in the Price field at the same time. (The user can then override the suggested price if necessary.)

Answer:

The easiest place to add extra assignments is by adding them under the More Assignments button. A good example of this is in Example 21. (BrowseInForm). The UpdateLineItems procedure does a lookup on the BrowseProducts procedure.

If you want to do more complicated things, then there is also an Embed point you can use, called AfterLookup.

Tip: Remember when embedding at this point in the code, you are working on the SessionQueue, not the actual file field. So If you want to set LIN:Price = PRO:RRP then the code needs to look like this:
p_web.SetSessionValue('Lin:Price',PRO:RRP)

There is a separate document discussing reports here.

Remember that all NetTalk has to do is convert your existing report output to PDF. So all the normal report questions (how to filter etc) are answered in exactly the same way you would for a normal Clarion report.

If you need to access settings, or parameters, set in the web interface remember that you do have access to the session queue when the report is running in web mode. You can access the queue using the normal syntax. TIP: Since the report can run in normal mode, and web mode, it's a good idea to check if the report is running in web mode, before accessing the session queue. This is done by testing the value of p_Web. For example

If Not p_Web &= Null
  ! we're in web mode
End

There is a  separate document discussing deployment included with the NetTalk documentation.

There is a style file called Error.Css which contains the style used by the errors page. Editing this CSS file is the first option for changing the layout, and style, of the errors page.

If you wish to change the text of the errors page, then override the MakeErrorPage method in the WebServer procedure. The text returned by this procedure contains the HTML sent back to the browser. See example 32.

Tip: Resist the urge to place the name of the missing file in the error message. This can lead to a security problem known as cross-site-scripting.

There're 2 things you need to do:

1: To override the NetTalk4 file update, find the ValidateRecord routine (this will override insert, change and deletes) and put the following code in:

ans = 0

2: You'll need to place the calls to your own filechange method in the ValidateInsert, ValidateUpdate and ValidateDelete methods.

You can add the parameters to the menu URL using the ?a=b&c=d syntax. For example

'BrowseCustomers?Current=1&Paidup=1'

The first parameter (after the page name) starts with a ? and after that you can have as many parameters as you like separated by a &.

Then in the Browse you need to store this parameter in a session variable so that the browse remembers it. Remember the browse procedure itself can get called many times in the life of the browse, so you can't rely on the parameter always being there. To store the parameter for later add the following to the top of the GenerateBrowse routine

If p_web.IfExistsValue('Current')
  p_web.StoreValue('Current')
End

Then in the browse make use of the SessionValue called Current. For example

'cus:current = ' & p_web.GetSessionValue('current')