Client–server model: Difference between revisions

Revision as of 14:55, 11 July 2025

Revision as of 14:55, 11 July 2025

Line 40:

=== Computer security ===

In a [[computer security]] context, server-side vulnerabilities or attacks refer to those that occur on a server computer system, rather than on the client side, or [[Man-in-the-middle attack|in between the two]]. For example, an attacker might exploit an [[SQL injection]] vulnerability in a [[web application]] in order to maliciously change or gain unauthorized access to data in the server's [[database]]. Alternatively, an attacker might break into a server system using vulnerabilities in the underlying [[operating system]] and then be able to access database and other files in the same manner as authorized administrators of the server.<ref name=oreilly>{{cite book |url=https://books.google.com/books?id=DyrLV0kZEd8C&q=client-side+OR+server-side&pg=PT17 |title=Computer Security Basics |edition=2nd |last1=Lehtinen |first1=Rick |last2=Russell |first2=Deborah |last3=Gangemi |first3=G. T. |publisher=[[O'Reilly Media]] |isbn=9780596006693 |date=2006 |access-date=2017-07-07}}</ref><ref name=n3tweb>{{cite web |url=https://n3tweb.wordpress.com/2015/10/15/week-4-is-there-a-difference-between-client-side-and-server-side/ |title=Week 4: Is There a Difference between Client Side and Server Side? |author=JS |website=n3tweb.wordpress.com |date=2015-10-15 |access-date=2017-07-07}}</ref><ref name=alpinesecurity>{{cite web |url=https://www.alpinesecurity.com/s/Alpine-Security-Decoding-the-Hack-Presentation-22-April-16.pdf |title=Decoding the Hack |last=Espinosa |first=Christian |website=alpinesecurity.com |date=2016-04-23 |access-date=2017-07-07 }}{{Dead link|date=March 2023 |bot=InternetArchiveBot |fix-attempted=yes }}</ref>

=== Examples ===

In the case of [[distributed computing]] projects such as [[SETI@home]] and the [[Great Internet Mersenne Prime Search]], while the bulk of the operations occur on the client side, the servers are responsible for coordinating the clients, sending them data to analyze, receiving and storing results, providing reporting functionality to project administrators, etc. In the case of an Internet-dependent user application like [[Google Earth]], while querying and display of map data takes place on the client side, the server is responsible for permanent storage of map data, resolving user queries into map data to be returned to the client, etc.

Web applications and [[web service|services]] can be implemented in almost any language, as long as they can return data to standards-based web browsers (possibly via intermediary programs) in formats which they can use.

==Client side==