A progress dialog will appear with commands sent to the server, headers received, cookie information, and more. This may be useful for debugging (for example, for debugging a redirect problem).
When the document has been successfully loaded into the editor, it can then be validated as if it were a local document or file.
Note that editing and saving the documents that have been opened with a URL will not change the document sent from the server. You will have to change the original document that is normally located on the web server. Often times this is done by uploading the new document to the web server by using an FTP program (a file transfer program).
Agent - The 'Agent' sets the 'User-Agent' header that is used to tell the web server what user agent or web browser (and possibly other information like operating system) is requesting the document. It can be used to "trick" the server into thinking a certain agent and OS is being used. Some web servers may return different pages depending on the agent. If this is the case, then specify what agent to use depending on what is being tested. If the web server doesn't care which agent is used (this is common), then specifying a particular agent should not matter.
Helpful external link: Understanding User-Agent Strings
•Firefox 1.5: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20060508 Firefox/22.214.171.124
•Firefox 3.0.1 on Vista 64-bit: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:126.96.36.199) Gecko/2008070208 Firefox/3.0.1
•Firefox 10.0.2 on Windows 8 64-bit: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
•Google Chrome 17.0 on Window 7 64-bit: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.78 Safari/535.11
•Internet Explorer 6: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
•Internet Explorer 7 on Vista 64-bit: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506; Media Center PC 5.0)
•Internet Explorer 9 on Windows 7: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)
•Internet Explorer 10 on Windows 8 (Metro UI): Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)
•Opera 9.62: Opera/9.62 (Windows NT 5.1; U; de) Presto/2.1.1
•Opera 11.60 on Windows 7 64-bit: Opera/9.80 (Windows NT 6.1; U; en) Presto/2.10.229 Version/11.60
•Internet Explorer 11 on Windows 8.1 64-bit: Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; rv:11.0) like Gecko
•Chrome 42.0 on Android 5.0: Mozilla/5.0 (Linux; Android 5.0.2; VS980 4G Build/LRX22G) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.109 Mobile Safari/537.36
•Safari on iPod touch with iOS 8.2: Mozilla/5.0 (iPod touch; CPU iPhone OS 8_2 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12D508 Safari/600.1.4
•Microsoft Edge on Windows 10: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.10586
POST Data - If you want to use a POST request instead of a GET request, then enter the POST data here (otherwise use '(none)' for no POST data). Enter name=value strings separated by '&' characters and use proper URL encoding. You can also press the edit button to enter one name=value field per line in an editor. When using the editor, do not use URL encoded values because they will be automatically URL encoded. Example: 'username=myname&password=mypassword'. Note: Data is posted using 'application/x-www-form-urlencoded'. (New v15.03)
Lang - This option is used to set the 'Accept-Language' header that is used to tell the web server what language the client prefers/accepts. Some web servers may be configured to return different pages depending on 'Accept-Language'. If this is the case, then specify what 'Accept-Language' value to use depending on what is being tested. If the web server doesn't care which language is accepted/requested (this is common), then the 'Accept-Language' value should not matter. (New v9.02)
•de = German
•en = English
•en-gb = English (United Kingdom)
•en-us = English (United States)
•en-us, en = English (United States) then English
•es = Spanish
Username & Password Options - If authentication is required then set the username and password to use when requesting the URL. Both HTTP and NTLM authentication are supported. The 'Use username and password' checkbox must be checked for these fields to be enabled.
•Use username and password - Check this box to enable the username and password fields for HTTP or NTLM authentication.
•HTTP/1.1 request - Check this box to make an HTTP/1.1 request, otherwise HTTP/1.0 is used. The default is HTTP/1.1. (New v12.0025)
•Close Progress Dialog When Done - Check this option if you want the progress dialog to automatically close when the download is complete (unless there is an error or problem). The default is not checked. (New v9.00)
•Keep Progress Dialog on Top - Check this option if you want the progress dialog to stay on top of the main editor window. The default is checked. (New v9.00)
(Pro, Std, Lite) Another way to check URLs and dynamic sites is to use the integrated web browser available in the standard and higher editions. While browsing with the integrated web browser, the source for the document being displayed is shown in an editor tab and can be easily validated. As you navigate through the web, you can also have the source automatically validated after each page is loaded. To do this, make sure that this feature is checked in the Editor Options. Using the integrated editor is a great way to check a website with dynamic pages such as those made by ASP, CFML, or PHP scripts.