-
Updated
Jul 15, 2020 - Vue
websocket
Here are 4,771 public repositories matching this topic...
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
PHP Version 7.1.9
The documentation says that Swoole coroutine cannot be used with xdebug, while developling applications xdebug is very helpful tool. For smaller application it may not be a problem but larger applications makes it necessary to use it.
My question is how can I debug applications while still using Swoole Coroutines ?
-
Updated
Jul 5, 2020 - JavaScript
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) []stringfunction 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
-
Updated
Jun 30, 2020 - PHP
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
-
Updated
Jul 4, 2020 - TypeScript
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 .viabilityChangedor
case .reconnectSuggestedWhat the point of them?
I can see viabilityChanged is called when we loss an
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.
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
So, in the last 3-4 hours i was searching for a memory leak in my app. After a complete code-review of my application code i decided to make a new simple app built on Ratchet WS server and see, if the problem persists. And it did!
The problem was, that whenever i created a WS connection, the connection class instances built in the background of the Ratchet were not destroyed! So on every ne
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.
-
Updated
Feb 5, 2020 - Go
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
docs: Add an index
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.
-
Updated
Jun 16, 2020 - PHP
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,
},
-
Updated
Jun 10, 2020 - JavaScript
It wasn't clear to me from this guide:
How to set an arbitrary http response status code like "500" maybe it could be improved upon? Thanks!
Improve this page
Add a description, image, and links to the websocket topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the websocket topic, visit your repo's landing page and select "manage topics."




Problem Description
The option --set doesn't work
Steps to reproduce the behavior:
The command mitmdump.exe -p 8088 --set ssl_version_client=all --set ssl_version_server=all doesn't change configuration
mitmdump.exe -p 8088 --options doesn't show changes
mitmdump.exe --options returns Error starting proxy server: OSError(98, 'Address already in use')
A default co