Bot releases are visible (Hide)
Published by NATS-CI over 5 years ago
Published by NATS-CI almost 6 years ago
CONNECT
trace.--signal
. Thanks to @pires for the contribution (#838)RemoteAddress()
to the CustomClientAuthentication
interface. Thanks to @ripienaar for the contribution (#837)logtime
. Thanks to @sazo for the report (#874, #879)Published by NATS-CI about 6 years ago
authorization {
myUserPerms = {
publish = {
allow = "*.*"
deny = ["SYS.*", "bar.baz", "foo.*"]
}
subscribe = {
allow = "foo.*"
deny = "foo.baz"
}
}
users = [
{user: myUser, password: pwd, permissions: $myUserPerms}
]
}
means that user myUser
is allowed to publish to subjects with 2 tokens (allow = "*.*"
) but not to subjects matching SYS.*
, bar.baz
or foo.*
. It can subscribe to subjects matching foo.*
but not foo.baz
.
Authorization Error
during configuration reload (#270)Published by NATS-CI over 6 years ago
rtt
field in /connz
monitoring endpoint. This measures the time between the server sent a PING to a client and the time it got the PONG back (#683)/connz
by client ID (CID). Example: http://localhost:8222/connz?cid=100
. Note that the CID is now sent back to the client. Client libraries have not yet been updated to report this to the application (#687)?state=closed
as in http://localhost:8222/connz?state=closed
. Possible values for state
are open
, closed
, all
. The result now includes a new field reason
that gives a reason why the connection was closed, for instance reason: Client
means that the client closed the connection (#692). For example: {
"cid": 2,
"ip": "::1",
"port": 63065,
"start": "2018-07-05T11:00:16.09747933-06:00",
"last_activity": "2018-07-05T11:00:21.441585272-06:00",
"stop": "2018-07-05T11:00:23.445200428-06:00",
"reason": "Slow Consumer (Write Deadline)",
"uptime": "7s",
"idle": "2s",
"pending_bytes": 8265,
"in_msgs": 0,
"out_msgs": 4178,
"in_bytes": 0,
"out_bytes": 534784,
"subscriptions": 1,
"lang": "go",
"version": "1.5.0"
},
/connz?sort=
sort options: start
, stop
and reason
(#705)foo
and publishes on foo
, it will receive those messages. To prevent this, the client's CONNECT
protocol includes a new boolean field named echo
that should be set to false
. The server is also sending a new int
field proto
in the INFO
protocol to the client, allowing the client library to decide if it can use the "echo" feature or not. Client libraries have not yet been updated to take advantage of this feature (#698)/subsz?subs=1
(#707). For instance: http://localhost:8222/subsz?subs=1
may return:"subscriptions_list": [
{
"subject": "foo",
"sid": "1",
"msgs": 1000,
"cid": 2
}
]
http://localhost:8222/subsz?subs=1&test=foo
would return the subscriptions_list
with subscriptions matching the test subject. If no match is found, the subscriptions_list
is not present.Published by NATS-CI over 6 years ago
ssl_required
field in INFO protocol. This was deprecated some time ago. The correct field to use is TLSRequired (#655)Published by NATS-CI over 6 years ago
/connz
and /routez
(#598)/connz
could be delayed for TLS clients still in TLS handshake (#604)Published by nats-ci-user over 6 years ago
*
and >
in subjects as literals. Thanks to @s921102002 for the report (#561)Published by nats-ci-user over 7 years ago
Published by nats-ci-user over 7 years ago
Great community effort! Special thanks to Elton Stoneman (@sixeyed) for his help in verifying that the Windows Docker images build properly!
GetTLSConnectionState()
in ClientAuth
interface. This returns the TLS ConnectionState
if TLS is enabled. Thanks to @cdevienne (#385)curve_preference
parameter to specify the preferred order (#412)write_deadline
parameter to make the deadline when flushing messages to clients configurable (#421, #488)MonitorAddr()
and ClusterAddr()
return the monitoring an route listener respectively (#512)Server.SetClientAuthMethod()
and Server.SetRouteAuthMethod()
(#474)tls: oversized record received
(#493)Published by nats-ci-user almost 8 years ago
max_connections
parameter (#387, #389)verify
was set to true (#337)max_connections
in previous releases, but it had no effect (#387, #389)MaxPending
option and max_pending_size
, max_pending
configuration parameters. Those were never used (#383)Published by derekcollison about 8 years ago
-a
command line or Options.Host
)-cluster
URL.Published by derekcollison about 8 years ago
Published by derekcollison over 8 years ago
Bug fix release.
Published by derekcollison over 8 years ago
Published by derekcollison almost 9 years ago
Published by derekcollison almost 9 years ago
Published by derekcollison about 9 years ago
Published by derekcollison about 9 years ago
I recut this release with Go1.4.2 since there are issues with Go1.5.
Published by derekcollison about 9 years ago
Published by derekcollison about 9 years ago