aboutsummaryrefslogtreecommitdiffstats
path: root/actioncable/CHANGELOG.md
Commit message (Collapse)AuthorAgeFilesLines
* [Fix #28751] Hash stream long stream identifiers when using Postgres adapterpalkan2017-07-061-0/+9
|
* Adds CHANGELOG for f55ecc6 [ci skip]Marc Rendl Ignacio2017-06-271-0/+9
|
* Cleanup CHANGELOGs [ci skip]Ryuta Kamizono2017-04-301-1/+2
| | | | | | * Remove trailing spaces. * Add backticks around method and command. * Fix indentation.
* Log any errors originating from the socketedwardmp2017-04-161-0/+6
|
* Start Rails 5.2 developmentMatthew Draper2017-03-221-45/+1
|
* Preparing for 5.1.0.beta1 releaseRafael Mendonça França2017-02-231-0/+2
|
* Add changelog entry for #27425 [ci skip]Chad Ingram2017-01-211-0/+6
|
* Small edits to actioncable/CHANGELOG.mdJon Moss2016-12-271-2/+2
| | | | | | [ci skip] - capitalize WebSocket
* Changelog editsVipul A M2016-11-121-4/+4
|
* Permit same-origin connections by defaultMatthew Draper2016-10-111-0/+7
| | | | | | | | | | | | | | | | | WebSocket always defers the decision to the server, because it didn't have to deal with legacy compatibility... but the same-origin policy is still a reasonable default. Origin checks do not protect against a directly connecting attacker -- they can lie about their host, but can also lie about their origin. Origin checks protect against a connection from 3rd-party controlled script in a context where a victim browser's cookies will be passed along. And if an attacker has breached that protection, they've already compromised the HTTP session, so treating the WebSocket connection in the same way seems reasonable. In case this logic proves incorrect (or anyone just wants to be more paranoid), we retain a config option to disable it.
* Merge pull request #26547 from ↵Matthew Draper2016-10-011-0/+8
|\ | | | | | | | | | | palkan/fix/actioncable-confirmation-race-condition Avoid race condition on subscription confirmation
* | Buffer writes to the cable socketsMatthew Draper2016-09-281-0/+5
|/ | | | | Otherwise, they can sometimes block, leading to reduced system throughput.
* Pass over changelogs [ci skip]Vipul A M2016-08-101-1/+1
|
* Correct changelog layoutMatthew Draper2016-07-091-8/+8
| | | | [ci skip]
* Insert changelog entry for #25615Matthew Draper2016-07-091-0/+7
|
* Merge pull request #25624 from tinco/actioncable_write_raceMatthew Draper2016-07-091-0/+5
|\ | | | | | | Fix race condition in websocket stream write
* | Add ActiveSupport::Notifications hook to Broadcaster#broadcastMatthew Wear2016-05-121-0/+3
|/ | | | | This addition of this notification hook will give users better visibility into the messages being sent over the PubSub adapter.
* Start Rails 5.1 development :tada:Rafael Mendonça França2016-05-101-87/+1
|
* Preparing for 5.0.0.rc1 releaseRafael Mendonça França2016-05-061-0/+5
|
* Prep Rails 5 beta 4eileencodes2016-04-271-0/+2
|
* Merge pull request #24224 from danielrhodes/actioncable-websocket-protocolsJeremy Daer2016-04-051-0/+20
|\ | | | | | | ActionCable protocol negotiation
* | Cable message encodingJeremy Daer2016-03-311-5/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Introduce a connection coder responsible for encoding Cable messages as WebSocket messages, defaulting to `ActiveSupport::JSON` and duck- typing to any object responding to `#encode` and `#decode`. * Consolidate encoding responsibility to the connection. No longer explicitly JSON-encode from channels or other sources. Pass Cable messages as Hashes to `#transmit` and rely on it to encode. * Introduce stream encoders responsible for decoding pubsub messages. Preserve the currently raw encoding, but make it easy to use JSON. Same duck type as the connection encoder. * Revert recent data normalization/quoting (#23649) which treated `identifier` and `data` values as nested JSON objects rather than as opaque JSON-encoded strings. That dealt us an awkward hand where we'd decode JSON strings… or not, but always encode as JSON. Embedding JSON object values directly is preferably, no extra JSON encoding, but that should be a purposeful protocol version change rather than ambiguously, inadvertently supporting multiple message formats.
* | Fix CHANGELOG entry [ci skip]Rafael Mendonça França2016-03-301-1/+1
| |
* | Add AS::Notifications and LogSubscriber to ActionCable::ChannelMatthew Wear2016-03-041-0/+4
|/ | | | | This commit adds ActiveSupport::Notifications instrumentation hooks and a LogSuscriber to ActionCable::Channel::Base.
* Fix CHANGELOG spacing [ci skip]Jeremy Daer2016-03-021-12/+12
|
* Accept JSON with no backslashes/escapingJon Moss2016-03-021-0/+5
| | | | | | | Fixes #22675 Allow channel identifiers and also data with no backslahes/escaping to be accepted by the subscription storer.
* Use AS::Executor / AS::Reloader to support reloading in ActionCableMatthew Draper2016-03-021-0/+5
|
* Update changelogJay Hayes2016-02-241-0/+4
|
* Add Ruby formatting to CHANGELOG entryclaudiob2016-02-241-4/+5
| | | | [ci skip]
* Preparing for 5.0.0.beta3 releaseeileencodes2016-02-241-0/+2
| | | | Adds changelog headers for beta3 release
* Allow for non-standard redis connectorsDavid Heinemeier Hansson2016-02-041-0/+7
|
* Add some Action Cable CHANGELOG entriesRafael Mendonça França2016-02-011-1/+10
| | | | | | And improve changelongs. [ci skip]
* Preparing for Rails 5.0.0.beta2Sean Griffin2016-02-011-0/+5
|
* Small doc update per RF [ci skip]Jon Moss2016-01-201-4/+5
|
* Add CHANGELOG.md entry for #22950Jon Moss2016-01-201-0/+8
| | | | [ci skip]
* No more no changes entries in the CHANGELOGsGenadi Samokovarov2015-12-211-4/+1
| | | | | | | | | | | | | | During the `5.0.0.beta1` release, the CHANGELOGs got an entry like the following: ``` * No changes. ``` It is kinda confusing as there are indeed changes after it. Not a biggie, just a small pass over the CHANGELOGs. [ci skip]
* Add CHANGELOG headers for Rails 5.0.0.beta1eileencodes2015-12-181-0/+5
|
* Initial stab at adding Action Cable to rails/masterDavid Heinemeier Hansson2015-12-141-0/+3
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 22:28:08 +0000