Revision as of 16:21, 14 May 2018 edit Steel1943 (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, Pending changes reviewers, Rollbackers, Template editors 228,915 edits →Scheduling Providers: fix templates ← Previous edit		Revision as of 16:21, 14 May 2018 edit undo Steel1943 (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, Pending changes reviewers, Rollbackers, Template editors 228,915 edits →Security Concerns: fix templates Next edit →
Line 48: When using a visitor based scheduling provider, users may inadvertently provide a possible venue for denial-of-service attacks. Also, if a script is written improperly, the script may unintentionally expose information about the server. When using a remote access scheduling provider, users usually{{~~really?~~peacock term\|date=December 2010}} have refined control over how communication takes place with the web server. If HTTP is used, the URL is sent in the clear over the wire but the data in the request is typically{{~~really?~~peacock term\|date=December 2010}} encrypted. This opens up the possibility of denial-of-service attacks and replay attacks. == References ==

Webcron: Difference between revisions