2.1.x redis roster #4
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This patch introduces a new config option - fqdn - to set the fully
qualified domain name of the host:
{fqdn, "foo.example.com"}.
This fixes a problem with Pidgin not being able to log in on a server
that used SRV records.
This fixes case when SockMod:recv() calls returns only part of first line of http request (GET/POST/OPTION/HEAD line). Before that change request like that (and if keep-alive was active, all further request) were dropped. This fixes EJAB-1537.
This was added in R13B3, lets roll our own implementation to make sure it works on older erlang versions.
This code adds case normalization step to https headers parsing, making it correctly use atoms for some special header no matter how upper/lower case letters are used in input string
This makes size of hibernated ejabberd_receiver a lot smaller (from ~290 words down to ~40).
SSL 2.0 is not used anywhere as it has security problems. Disable it unconditionally both in server and client mode. This does _not_ disable support for SSL 2.0 compatible client hello which still will be accepted in the server mode.
Disable: - export ciphers - broken by design, 40 and 56 bit encryption - low encryption ciphers - 56 and 64 bit encryption - SSLv2 ciphers - some ciphers using MD5 MAC
TLS driver impovements
Rosters is stored in a hash as following:
{
"rosterusers::username1": [
{"user2@server2": "nick2::subscription2::ask2::askmessage2::group2"},
{"user3@server3": "nick3::subscription3::ask3::askmessage3::group3"},
{"user3@server4": "nick4::subscription4::ask4::askmessage4::group4"}
],
"rosterusers::username2": [
{"user2@server2": "nick2::subscription2::ask2::askmessage2::group2"},
{"user5@server5": "nick5::subscription5::ask5::askmessage5::group5"},
{"user3@server4": "nick4::subscription4::ask4::askmessage4::group4"}
]
}
Roster is stored in a redis hash as following:
{
"rosterusers::username1": [
{"user2@server2": "nick2::subscription2::ask2::askmessage2::group2"},
{"user3@server3": "nick3::subscription3::ask3::askmessage3::group3"},
{"user3@server4": "nick4::subscription4::ask4::askmessage4::group4"}
]
}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
mod_roster_redis : allow ejabberd to store roster in a redis hash (including support of redis proxy twemproxy aka nutcracker). This module uses eredis.
Thx.