diff options
| author | Yuji Yaginuma <yuuji.yaginuma@gmail.com> | 2018-09-04 20:06:09 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-09-04 20:06:09 +0900 |
| commit | 63c6943131189c902485f725b465b48ebea14b09 (patch) | |
| tree | 8c919c225d179240bb722391b595142e01578ee8 /actioncable | |
| parent | e6ba30efbf107954db2707410d78d77680d69995 (diff) | |
| parent | c9fd722851d97a3cc267a59952a4930a1605a3dc (diff) | |
| download | rails-63c6943131189c902485f725b465b48ebea14b09.tar.gz rails-63c6943131189c902485f725b465b48ebea14b09.tar.bz2 rails-63c6943131189c902485f725b465b48ebea14b09.zip | |
Merge pull request #33789 from nisusam/update_hijacking_link
Update link for `Rack socket hijacking API`
Diffstat (limited to 'actioncable')
| -rw-r--r-- | actioncable/README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/actioncable/README.md b/actioncable/README.md index a05ef1dd20..d6893dbab1 100644 --- a/actioncable/README.md +++ b/actioncable/README.md @@ -425,7 +425,7 @@ The above will start a cable server on port 28080. ### In app -If you are using a server that supports the [Rack socket hijacking API](http://www.rubydoc.info/github/rack/rack/file/SPEC#Hijacking), Action Cable can run alongside your Rails application. For example, to listen for WebSocket requests on `/websocket`, specify that path to `config.action_cable.mount_path`: +If you are using a server that supports the [Rack socket hijacking API](https://www.rubydoc.info/github/rack/rack/file/SPEC#label-Hijacking), Action Cable can run alongside your Rails application. For example, to listen for WebSocket requests on `/websocket`, specify that path to `config.action_cable.mount_path`: ```ruby # config/application.rb @@ -459,7 +459,7 @@ support, which means you can use all your regular Rails models with no problems as long as you haven't committed any thread-safety sins. The Action Cable server does _not_ need to be a multi-threaded application server. -This is because Action Cable uses the [Rack socket hijacking API](http://www.rubydoc.info/github/rack/rack/file/SPEC#Hijacking) +This is because Action Cable uses the [Rack socket hijacking API](https://www.rubydoc.info/github/rack/rack/file/SPEC#label-Hijacking) to take over control of connections from the application server. Action Cable then manages connections internally, in a multithreaded manner, regardless of whether the application server is multi-threaded or not. So Action Cable works |