Revision as of 17:48, 11 February 2023 edit Kvng (talk \| contribs) Extended confirmed users, New page reviewers 100,229 edits Reverted good faith edits by 103.76.190.138 (talk): No significant improvement. runon. Tags: Twinkle Undo ← Previous edit		Revision as of 23:12, 10 March 2023 edit undo Citation bot (talk \| contribs) Bots 5,010,880 edits Alter: template type. Add: doi, year, website, authors 1-2. editors 1-2. Removed parameters. Some additions/deletions were parameter name changes. \| Use this bot. Report bugs. \| Suggested by Superegz \| Category:Network protocols‎ \| #UCB_Category 42/343 Next edit →
Line 11: == Examples == An [[HTTP]] server can understand each request in isolation.<ref>{{cite ~~web~~journal \|url=http://tools.ietf.org/html/rfc7230 \|title=RFC 7230 - Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing\|~~work~~website=ietf.org \|year=2014 \|doi=10.17487/RFC7230 \|access-date=20 August 2015\|editor-last1=Fielding \|editor-last2=Reschke \|editor-first1=R. \|editor-first2=J. \|last1=Fielding \|first1=R. \|last2=Reschke \|first2=J. }}</ref> Contrast this with a traditional [[File Transfer Protocol\|FTP]] server that conducts an interactive session with the user. During the session, a user is provided a means to be authenticated and set various variables (working directory, transfer mode), all stored on the server as part of the session state.

Stateless protocol: Difference between revisions