A free request-test brief for an endpoint you control, with expected routing, response checks, and a stop condition.
Published October 15, 2026 · Programming Securely · Original exercise with illustrative examples
Define one authorized request
Choose an endpoint you own or are authorized to test, an HTTP method, and a synthetic payload. Record the expected destination and avoid real credentials or customer records in a planning worksheet. Simple Load Balancer forwards requests to configured, administrator-approved targets; a plan should identify the intended target rather than rely on a similarly named environment.
Check transformations and side effects
Write which headers, query parameters, or body fields should change and which should stay intact. A successful HTTP response does not prove that a mutation happened only once or reached the intended environment. Use a non-mutating request when it answers the question. If a test must change state, arrange a bounded test record and verify the expected effect in the authorized destination.
Choose success and stopping conditions
Specify the response status and a small piece of response evidence you expect, then state when to stop. An unexpected destination, authentication failure, or duplicate operation is a reason to investigate before increasing traffic. This worksheet sends no request, probes no host, and changes no load balancer. It produces a local brief for a controlled test you choose to perform elsewhere.
Worked example
A small situation to try
Illustrative test: an operator plans one GET request to an owned staging health endpoint. They expect the proxy to preserve a harmless request identifier and return the staging marker. The test stops if the marker is missing or identifies another environment. No production mutation or customer payload is involved.
Try it here · No account needed
Your working notes
This worksheet does not send your writing to Simple Load Balancer, save it to an account, or store it in your browser. Notes are cleared when you leave or reload this page. Download a text copy if you want to keep them.
Use a synthetic description; omit tokens and private host inventories.
Name the harmless fields that should change or stay intact.
Record status and a destination marker, not just “works.”
State what would stop the test before any traffic increase.
What to do next
Use what you learned
Verify authorization and the intended environment before sending any request.
Run one bounded test and compare the actual evidence with the brief.
Return to the product for its current features and availability. This independent worksheet changes no account data.
About this guide
Published by Programming Securely for Simple Load Balancer. Product descriptions are checked against this project’s documentation. Examples are fictional and are kept separate from observed product behavior. The worksheet helps you prepare a note; it does not replace the product’s current documentation.
For a correction, use the product’s contact or support link on its homepage and name this guide and the passage that needs review.