Is your feature request related to a problem? Please describe.
The {{< highlight none >}} :~q:foo:bar {{< / highlight >}} blocks don't work on GitHub. It's confusing and makes the code examples almost useless on GitHub itself. And also in your code editor if you have Markdown syntax highlighting with embedded highlighting for nested code.

Describe the solution you'd like

It'd be ne

Issue Description

I updated echo in one of my projects. After that my static configuration didn't work without changes. Before it automatically resolved to an existing index.html. After that I had to point to that file.

My code was something like that:

docsGroup := e.Group("")
docsGroup.Static("/", "docs")

In docs is an index.html which was delivered when no path was given

Please answer these questions before submitting your issue. Thanks!

1. What did you do? If possible, provide a recipe for reproducing the error.

read Chinese and English documentation

1. What did you expect to see?

I expected to find best practice for production usage

1. What did you see instead?

nothing

1. What version of Swoole are you using (php --ri swoole)?

latest.

Thanks for publishing this! How about adding it to GitHub.com/topics/terminal-share alongside similar tools by adding that topic to this repo? Thank you :-)

Points to cover

• An application can handle subprotocol negotiation on its own by setting the Sec-Websocket-Protocol response header. The Subprotocols(r *http.Request) []string function is helpful here.
• Set u.Subprotocols for builtin subprotocol negotiation. Builtin negotiation overrides a subprotocol specified in the response header (it would have been better to return an error, but it

Hello!

When text line in list is too long and part of it is moved on the next line, list number is placed on the last line. When I use <br>, list number is placed on the first line of multiline text.

Demo is below:

Demo text:

1. [ ] task 1
2. [ ] task 2 task 2 task 2

The one line description is too ambigious.

Can we have a verbose document explaining what all the close messages mean and what are the possible causes of them included likelyness of each cause.

For example does "server lost session" mean that I restarted the server or could it also be a browser / proxy / ws bug/issue?

The example code does not work as intended.

Steps to reproduce

Use the example code:

var express = require('express');
var proxy = require('http-proxy-middleware');

var app = express();

app.use(
  '/api',
  proxy({ target: 'http://www.example.org', changeOrigin: true })
);
app.listen(3000);

Expected behavior

This should create a proxy for /api to `http

See http://blog.erlang.org/ssl-logging-in-otp-22/ for a full description.

One could enable debug logging in Cowboy to see all the packets transmitted and what Cowboy thinks of them, something like that. Could make some client issues obvious in particular.

Hello, I'm updating from 3.1.0 to 4.0.3.

Do we have some documentation available (more advance guide than README.md)? More precisely about WebSocketDelegate?

I don't really know what I should do when these methods are called:

case .viabilityChanged

or

case .reconnectSuggested

What the point of them?

I can see viabilityChanged is called when we loss an

This is wonderful work and I'm very grateful to find this repo. I'm having difficulty understanding how to scale to multiple networks following the SCC guide and also confused on the recommended architecture. The main issue is clients on separate servers are not finding messages from each other.

On a gcloud instance, i start the state (node server.js), broker( SCC_STATE_SERVER_HOST='[google giv

In the docs about supporting binary messages, it is stated that the controller should implement Ratchet\WebSocket\MessageComponentInterface.

However, if using Ratchet\App, when adding a new route with this controller, the WsServer is not created, since the [`$controller instanceof MessageComponentInterfa

we don't need a event name.

how to add a global message listener. all event or without event message can send to here.

<img width="287" alt="default" src="https://user-images.githubusercontent.com/2519544/42929452-af25cccc-8b6c-11e8-903d-46fbaaacae1d.png"

Based on feedback we collected Centrifugo docs are not complete and hard to understand for beginner developers.

I think it's obvious that we need to improve things here. Since I wrote it myself my vision is a bit blurred and I want to understand what are the main weak points of current docs. Will appreciate help with this.

Version:
^7.0.0

Environment:
any os

Related to #646, not an error but a respectful request for a documentation update:

pingInterval is hard-coded to false in createSocket method (so the dummy primus server does not run heartbeats - understood).

I took a trip down the rabbit hole recently - figuring out why the heartbeat check was not happening on the client, and I admit freely that t

Currently, it is a very long page that'd be easier to navigate and search with an index. Also, maybe split up docs in small consumable amount by using different pages?

Some people seem to read https://html.spec.whatwg.org/multipage/forms.html#dom-form-nameditem as implying that a new nodelist should be returned each time when there are multiple matching elements. That's not the intent, I assume, and it might be worth clarifying the spec to make it clear.

All browsers I tested (Firefox, Chrome, Safari) return the same nodelist on multiple accesses.

Describe the bug
useConnectionNamespace isn't an option of Vuex, you can assign it only to the global option object.

Expected behavior
useConnectionNamespace is documented as global option.

Additional context
this one works:

Vue.use(new VueSocketIO({
    debug: true,
    connection: 'http://localhost:3000/overview',
    vuex: {
        store,
    },
    

It wasn't clear to me from this guide:

https://kemalcr.com/guide/

How to set an arbitrary http response status code like "500" maybe it could be improved upon? Thanks!