bpytlik

Fix #184 abao should understand security schemes

5

This fixes issue #184. Please let me know if you have any issues with it or any additional testing information you'd like to have.

abao should understand security schemes

6

As part of our API, we have a security scheme we use for some endpoints. Since abao doesn't know about those security schemes, it doesn't have a way of testing...

Session examples need updating

3

Both session examples in the examples directory use the express 3.X approach of `express.cookieParser` and `express.session`. Since express was updated to 4.x in May, these examples should be updated to...

This fixes both issue #101 and issue #99.

While authorizing a socket.io request after upgrading to the tip of express.io, I kept getting a 403 when my sio client tried to connect to the server. The problem is...

After fixing issue #99 I discovered that when I reloaded my page, I got the following stack trace from express.io: > /node_modules/cookie-parser/index.js:25 > if (req.cookies) return next(); > ^ >...

support rerouting sockets

2

This is a fix for issue #59. It adds the ability to make a route available for all existing sockets when it is routed. It passes the existing test suite...

I'd like my server to be able to dynamically create and destroy rooms as clients come and go from particular rooms. The clients always have a socket-io connection open. They...

support for volatile?

1

Maybe I'm just missing it, but I'm not seeing a way to use express.io to do a volatile emit or broadcast. Ideally, I'd like to be able to do a...

This is the simplest way to fix the issue from my perspective. I'm happy to use a different approach, for example using subclasses instead, but I'd like guidance about the...