Comments (5)
Section 4 should also have its MUST
in The HTTP [RFC2616] response from the publisher MUST include at least one Link Header
reduced to a SHOULD
to better indicate this possibility.
Currently it both specifies that you MUST
use a header and specifies what you MAY
use if there is no header. But no header means a non-compliant publisher with the current language, so the need for a fallback seems contradictory by the current spec. (I guess the fallback is there to support PuSH 0.3 publishers?)
from pubsubhubbub.
Thanks for the notes, @voxpelli
oh also @tantek asked me to tag him in this
from pubsubhubbub.
@aaronpk I agree with your change. It's clearer and will avoid any confusion.
@voxpelli I understand your comment and I agree that things are a bit blurry when there are no link headers. Basically think compliance with 0.4 MUST mean that HTTP link headers are used. However, it is possible to also include Links in other parts (such as the HTML <head>
section, or <atom:link>
elements for RSS/Atom feeds... And, as you've identified, when there are no headers, I would much rather let implementers fallback to 0.3 (even though that spec does not apply to HTML).
Basically, inline with the robustness principle, I'd rather have a "strict" spec (with the requirement for link headers) and more flexible implementations (which would tolerate missing Link Headers, as long as there are some in the html/rss). Does it make sense?
from pubsubhubbub.
I made a PR for this change! ^^
from pubsubhubbub.
Thanks, merged!
from pubsubhubbub.
Related Issues (20)
- Define Specific Content-Types HOT 1
- PubSubHubbub Core 0.4: Validation vs. verification of intent HOT 1
- PubSubHubbub Core 0.4: Fat pings vs. normal pings HOT 3
- PubSubHubbub Core 0.4: Verification of intent vs. "denied" HOT 1
- PubSubHubbub Core 0.4: Verifying during subscription request HOT 1
- PubSubHubbub Core 0.4: Acceptance of a subscription request HOT 7
- PubSubHubbub Core 0.4: X-Hub-Signature HOT 1
- Failed verification of intent: Send "denied" message to subscriber's callback? HOT 1
- Specify how publishers notify hubs HOT 19
- Do not require rel=self for discovery HOT 6
- Subscription Response Details regarding Validation HOT 4
- PuSH 0.4 recommends old SHA1 signatures HOT 2
- Make PuSH a "living" spec HOT 5
- Looking for server code HOT 3
- Silent Rate-Limiting by the Google PubSubHubbub Hub? HOT 5
- Google Hub's Subscriber Diagnostics Seems down HOT 4
- its stop working for my blogger HOT 1
- is this deprecated ?
- Feature Request: Youtube push notifications for user activity on my channel HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pubsubhubbub.