What is a Valid URL for a Load Test

Enter the URL for your website or API (i.e. http(s)://www.example.com). Only public URLs are supported. Local URLs: http://localhost, 192.x.x.x addresses or any local ports will not be reached.

A public URL refers to a web address that is accessible from the open internet. It contrasts with private or local URLs, which are typically reserved for internal networks and cannot be accessed from outside that network.

In the context of load testing or any testing that involves a tool or service external to your environment, a public URL is necessary because the testing tool needs to be able to send requests to and receive responses from the target server. If the URL is private or local, the testing tool, being outside of your internal network, will not be able to access it.

Here's a breakdown:

1. Public URL: It's a global address accessible from any place on the internet. A typical format is:

• http(s)://www.example.com

2. Local URLs: These are addresses that typically point to a device's local environment or a private network. They are not accessible from the broader internet. Examples include:

• http://localhost – Refers to the device you're currently using. Often used for local development.
• 192.x.x.x addresses – These are private IPv4 addresses used within a local network. They can't be accessed from outside that network.
• 10.x.x.x, 172.16.x.x to 172.31.x.x, and 192.168.x.x are all private IP address ranges that are often used within local networks.

3. Ports: Local URLs might also specify ports, especially when working with specific services or applications in a development environment. For instance:

• http://localhost:8080
• http://192.168.1.10:3000

When you're prompted to enter a URL for testing, as the provided example suggests, you should ensure that the URL is public. Local URLs like http://localhost or IP addresses from private ranges like 192.x.x.x won't be reachable by the external testing service.

Valid HTTP requests

Valid URLs for Websites or API Endpoints

• example.com
• www.example.com
• http://example.com
• http://www.example.com
• http://www.example.com/#hash1
• http://www.example.com?query1=value1&query2=value2
• http://www.example.com?query1=value1&query2=value2#hash1
• http://api.example.com/v2/resources/1?query1=value1&query2=value2

Valid HTTPS request

Valid URLs for Websites or API Endpoints

• https://example.com
• https://www.example.com
• https://www.example.com/#hash1
• https://www.example.com?query1=value1&query2=value2
• https://www.example.com?query1=value1&query2=value2#hash1
• https://api.example.com/v2/resources/1?query1=value1&query2=value2