Server-side: Difference between revisions

Help

From Wikipedia, the free encyclopedia

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Inline

Latest revision as of 22:49, 21 March 2024

Redirect to:

Client–server model#Server-side

This page is a redirect. The following categories are used to track and monitor this redirect:

From a merge: This is a redirect from a page that was merged into another page. This redirect was kept in order to preserve the edit history of this page after its content was merged into the content of the target page. Please do not remove the tag that generates this text (unless the need to recreate content on this page has been demonstrated) or delete this page.
- For redirects with substantive page histories that did not result from page merges use {{R with history}} instead.

With possibilities: This is a redirect from a title that potentially could be expanded into a new article or other type of associated page such as a new template. The topic described by this title may be more detailed than is currently provided on the target page or in a section of that page.
- When the target page becomes too large, or for any reason a new page would be an improvement, this redirect may be replaced with an article, template or other project page that is carved out of the target page. See also {{R to section}} and use together with this rcat when appropriate.
- If the topic of the redirect is not susceptible to expansion, then use other rcats such as {{R to section}} or {{R to list entry}} when appropriate.
- Since a new page may be created, links to this redirect should not be replaced with a direct link to the target page. To make redirects to this page, use {{R avoided double redirect}}.
- {{R printworthy}} should be used together with this template when applied to a redirect in mainspace.
- When used on a template redirect, it will automatically populate Category:Template redirects with possibilities.

From a printworthy page title: This is a redirect from a title that would be helpful in a printed or CD/DVD version of Wikipedia. See Wikipedia:Printability and Version 1.0 Editorial Team for more information.

When appropriate, protection levels are automatically sensed, described and categorized.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Server-side&oldid=1214903994"

Hidden categories:

@@ Line 1: / Line 1: @@
+#REDIRECT [[Client–server model#Server-side]]{{R shell|{{R from merge}}
-{{Refimprove|date=December 2016}}
+{{R with possibilites}}
+{{R printworthy}}}}
-'''Server-side''' refers to operations that are performed by the [[Server (computing)|server]] in a [[client–server]] relationship in a [[computer network]].<ref name=stackexchange>{{cite web|url=http://softwareengineering.stackexchange.com/questions/171203/what-are-the-differences-between-server-side-and-client-side-programming|title=What are the differences between server-side and client-side programming?|website=softwareengineering.stackexchange.com|access-date=2016-12-13}}</ref><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}}</ref>
-==General concepts==
-Typically, a server is a [[computer application]], such as a [[web server]], that runs on a remote [[server (computing)|server]], reachable from a [[user (computing)|user]]'s local [[computer]], [[smartphone]], or other device.  Operations may be performed server-side because they require access to information or functionality that is not available on the [[client (computing)|client]], or because performing such operations on the [[client-side|client side]] would be slow, unreliable, or [[computer security|insecure]].
-Client and server programs may be commonly available ones such as free or commercial [[web server]]s and [[web browser]]s, communicating with each other using standardized [[protocol (computing)|protocols]].  Or, [[programmer]]s may write their own server, client, and [[communications protocol]] which can only be used with one another.
-Server-side operations include both those that are carried out in response to client requests, and non-client-oriented operations such as maintenance tasks.
-==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 /><ref name=n3tweb /><ref name=alpinesecurity />
-==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.
-In the context of the [[World Wide Web]], commonly encountered server-side computer languages include:<ref name=stackexchange />
-* [[C Sharp (programming language)|C#]] or [[Visual Basic]] in [[ASP.NET]] environments
-* [[Java (programming language)|Java]]
-* [[Perl]]
-* [[PHP]]
-* [[Python (programming language)|Python]]
-* [[Ruby (programming language)|Ruby]]
-* [[Node.js]]
-* [[Swift (programming language)|Swift]]
-However, 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.
-==See also==
-*[[Client-side]]
-*[[Server-side scripting]]
-*[[Server Side Includes]] (SSI)
-==References==
-{{Reflist}}
-[[Category:Servers (computing)]]
-{{network-software-stub}}