FServers
A protocol for transferring files between client and server. Basic FTP encrypts neither the connection nor credentials. FTPS adds TLS; SFTP is a separate protocol associated with SSH. These names are not interchangeable.
Definition and sources→GServers
Principles for managing systems through declared, versioned state and automatic reconciliation. A repository stores desired state while controllers detect drift.
Definition and sources→GServers
A platform for visualising and analysing observability data from multiple sources. Dashboards help interpretation but require correct data and alerting rules.
Definition and sources→HServers
Storage using rotating magnetic platters. Mechanical access affects latency; capacity, reliability and performance depend on the specific model.
Definition and sources→HServers
Designing a service to limit disruption despite component failures. Redundancy needs tested failover and removal of single points of failure; it does not eliminate risk.
Definition and sources→HServers
Providing resources needed to operate a website or application. Hosting involves more than storage: computing, networking and maintenance matter. Selection depends on project requirements and the provider's responsibilities.
Definition and sources→HProgramming / Servers
An Apache configuration file affecting a directory when the server permits overrides. It can control redirects and access. It is not universal to every hosting server; Nginx does not read it like Apache.
Definition and sources→HServers / Websites
An application protocol using requests and responses, including for websites and APIs. It defines methods, headers and statuses. Protocol statelessness does not prevent applications from implementing sessions.
Definition and sources→HServers / Websites
An HTTP status indicating a resource has moved permanently. The server normally provides the new address in Location. It is a redirect, not an error, and does not guarantee preserved search rankings.
Definition and sources→HServers / Websites
An HTTP status indicating a temporary redirect while the original address remains the reference. It is not an error. Indexing effects depend on context rather than a blanket rule that 302 never affects search.
Definition and sources→HServers / Websites
An HTTP status indicating that the server refuses the request, possibly because of permissions or access rules. A TLS certificate failure is not a 403 response. Resolve permissions with the administrator instead of bypassing protections.
Definition and sources→HServers / Websites
An HTTP status indicating that a resource was not found or its existence is not disclosed. Check addresses and links. DNS failure happens at a different stage and is not itself an HTTP 404 response.
Definition and sources→HServers / Websites
A general HTTP status signalling an unexpected server-side problem. It does not identify a specific cause. Diagnosis requires safe inspection of logs and configuration; updating PHP at random is not a universal fix.
Definition and sources→HServers / Websites
An HTTP status indicating that the server does not support, or refuses to support, the major protocol version used in the request. It concerns HTTP, not the browser version or a general network outage.
Definition and sources→HServers / Websites
HTTP carried over a TLS-protected connection. It protects transmission confidentiality and integrity and supports server authentication. A padlock does not establish the owner's honesty or protect against every application defect.
Definition and sources→HServers
An architecture combining private or on-premises environments with public cloud. Integration, management and data flow matter, not merely having two providers.
Definition and sources→IServers
A backup protected against changes or deletion for a defined retention period and policy. Immutability does not replace permission separation or restoration tests.
Definition and sources→IServers
A service model supplying infrastructure such as virtual machines, networks and storage. Customers typically remain responsible for operating systems and applications.
Definition and sources→IServers
Describing infrastructure in versioned files rather than only manual configuration. It supports repeatability and review; secrets and state require separate protection.
Definition and sources→IServers
A tool automating application installation and management on hosting. Automated setup does not remove responsibility for updates, configuration and backups.
Definition and sources→IInternet / Servers
Protocols for addressing and forwarding packets between networks, notably IPv4 and IPv6. IP itself guarantees neither delivery nor ordering nor encryption.
Definition and sources→IProgramming / Projects
Tools and activities for processing, storing and communicating information. Business IT includes applications, devices, networks and their maintenance. It extends beyond programming.
Definition and sources→KServers
An analysis and visualisation interface in the Elastic ecosystem. It provides index exploration and dashboards; permissions should restrict sensitive-log access.
Definition and sources→KServers
A container-application orchestration system managing declared state. It automates operations but needs infrastructure expertise and is not necessary for every project.
Definition and sources→