New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unconnected operation not yet implemented #328

Open
sbordet opened this Issue Jan 23, 2012 · 2 comments

Comments

Projects
None yet
1 participant
@sbordet
Copy link
Member

sbordet commented Jan 23, 2012

From what I can infer by looking at the source code, unconnected operation is not supported as described by the Bayeux protocol spec.

A test shows that this is indeed true:

REQUEST:
POST /cometd HTTP/1.1
Host: localcluster
Content-Type: application/json;charset=UTF-8
User-Agent: PHP control::publish
Content-Length: 118 bytes
Connection: Close

[{"channel":"/chat/demo","id":"213","data":{"dedupId":"aa55e25af2ebb22646952045219cdee3","msg":{"id":1`}]

REPLY:
HTTP/1.1 200 OK
Content-Type: application/json;charset=UTF-8
Connection: close
Server: Jetty(7.6.0.RC5)

[{"id":"213","error":"402::Unknown client","successful":false,"channel":"/chat/demo"}]

@sbordet

This comment has been minimized.

Copy link
Member Author

sbordet commented Jan 23, 2012

Originally reported by 8u45amnu on 2012-01-23T11:21:31Z

@sbordet

This comment has been minimized.

Copy link
Member Author

sbordet commented Jan 26, 2012

sbordet on 2012-01-26T06:50:19Z:
True, this feature is not implemented yet.

The main objection at implementing this (although the protocol does allow it) is that anyone will be able to publish without control, creating a vector for DoS attacks.

What use case do you have in mind, that will find a unconnect publish to be useful without opening for DoS ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment