This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25727 - "Fetch end points must enforce restrictions on a..."
Summary: "Fetch end points must enforce restrictions on a..."
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Fetch (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+fetchspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-15 16:15 UTC by James Graham
Modified: 2014-05-16 12:54 UTC (History)
1 user (show)

See Also:


Attachments

Description James Graham 2014-05-15 16:15:19 UTC
http://fetch.spec.whatwg.org/#requests

[[
Fetch end points must enforce restrictions on a request's method and author headers. 
]]

It's very unclear what this is supposed to mean. Presumably it's a requirement on algorithms (in specs) that call fetch. However calling these "fetch end points" is very confusing because an "end point" is already a term of art in HTTP-based services and refers to something on the server side. You should create a new term and clearly define it so that it's obvious what the intention here is.