In what cases is it appropriate to pass parameters via GET, and in what cases should it not be done?

Using GET parameters is advisable in the following cases:

• Retrieving data (reading): GET requests are idempotent and should not change the state on the server. This is the primary method for obtaining resources or information.
• Caching: Browsers and proxy servers can cache GET requests, which speeds up subsequent requests to the same URI.
• Creating links: Parameters in the URL facilitate creating direct links to specific data views or search results.
• Small amount of data: When transmitting a small volume of non-sensitive data.
• Shareable requests: When the request result can be easily shared with another user via a link.

GET parameter transmission should not be used in the following cases:

• Transmitting sensitive data: Passwords, personal data, authorization tokens, and any other information that should not be visible in the URL, browser history, or server logs.
• Large volume of data: URLs have length limitations (although dependent on the browser/server, they do exist).
• Changing server state: GET requests should not cause changes in state (creation, update, deletion of resources). For this, POST, PUT, DELETE methods are used.
• File download: Transmitting file contents via URL parameters is impractical and non-standard.
• Action links in email campaigns: Links in emails that perform actions on the server (e.g., unsubscribe) should not use GET to avoid accidental actions when scanning the email with antivirus or email clients.