| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
More in line with the other tests
|
|
|
|
|
| |
That whole condition stanza was shown as angry red, I think it's
something with 'enum' being a key word in Teal.
|
|
|
|
| |
This is a bit special in Lua as tables are not limited to string keys
|
|
|
|
| |
This is a bit cleaner, I think
|
| |
|
|
|
|
| |
This may have been what got me confused about "items" being an array.
|
|
|
|
| |
And apparently I had mistaken this for an array
|
|
|
|
|
|
| |
Apparently a schema must be either an object or a boolean. Not sure
where I got this string shortcut from, but I think I will keep it as it
is very convenient.
|
|
|
|
|
|
| |
Upon re-reading the JSON Schema spec, I found that 'items' wasn't a
union of an array of schemas or a single schema, not sure where I got
that from.
|
|
|
|
|
|
|
| |
attribute matters
E.g. <feature var='foo'/> in XEP-0030 and some other simple
specifications.
|
| |
|
|
|
|
|
| |
Useful for certain enum-like uses where the element name is the relevant
information, e.g. chat states.
|
| |
|
|
|
|
| |
Based on the XML support in the OpenAPI specification.
|
| |
|
|
|
|
|
| |
Compiled Lua targets included in parallel in order to not add a hard
dependency on Teal, at least not yet.
|
|
|
|
|
|
|
|
| |
Enables writing code in Teal that is aware of the interfaces and
function prototypes in these other utils.
Could also be used to do type checks on Lua sources, but this tends to
have a lot of noise.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fixes mistake introduced in 5a71f14ab77c that made it so this ready()
newer got called and thus it would be stuck waiting for it.
Looks like the kind of thing that could have been introduced by a merge
or rebase.
Thanks MattJ
|
|
|
|
|
|
|
|
|
| |
XEP-0060 6.2.2
This is a MAY but it makes it nice and symmetric with the subscription
response. Reduces the need to remember which node you unsubscribed from.
Explicit > implicit etc.
|
| |
|
|
|
|
| |
Test all fields in both directions in order to catch #1642
|
|
|
|
| |
At least I think :text_tag improves readability.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Test procedure:
$ prosodyctl shell 'server:version()'
Expect:
> OK: hg:926d53af9a7a
$ prosodyctl shell 'server:version()' 'hello'
Expect:
> Only one command is supported as argument
$ prosodyctl shell 'lorem ipsum'; echo $?
Expect:
> Sorry, I couldn't understand that... console:1: syntax error near 'show'
> 1 (error code)
Thanks Menel for mentioning the feature
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Looked in the wrong table
Test procedure:
$ prosodyctl shell --quiet
Expect:
Prosody>
(No banner)
|
|
|
|
|
| |
Turns out 'extra' is, at least for mod_s2s, the same table for *all*
connections.
|
|
|
|
| |
Turns out it doesn't work with zero.
|
|
|
|
|
| |
In "opportunistic writes" mode, prevents ondisconnect from happening
while writing the stream closing tag.
|
|
|
|
|
|
|
|
| |
Should prevent errors in certain places where it logs
session.direction captialized using gsub.
Might cause bugs tho, but then the session is destroyed so maybe it
doesn't matter?
|
|
|
|
|
|
| |
Both session.incoming and session.outgoing are truthy here, but
session.direction indicates the "real" direction in the way that matters
for the order of events when opening or closing streams.
|
|
|
|
| |
Supported in the DNS layer, this isn't RFC about how to use it in XMPP.
|
| |
|
|
|
|
|
|
| |
Disabled DANE by default, since it needs extra steps to be useful. The
built-in DNS stub resolver does not support DNSSEC so having DANE
enabled by default only leads to an extra wasted DNS request.
|
| |
|
|
|
|
| |
To highlight how many these are
|
|
|
|
| |
See 6e051bfca12d
|
|
|
|
|
| |
Trying to move everything relating to proxies and X-Forwarded-Foo into a
single place.
|
|
|
|
|
|
|
|
| |
Because it already sets request.secure, which depends on the connection,
just like the IP, so it makes sense to do both in the same place.
Dealing with proxies can be left to mod_http for now, but maybe it could
move into some util some day?
|
|\ |
|
| |
| |
| |
| |
| | |
8603011e51fe optimized out more than just the loop, leaving the .ip
field blank when the request wasn't from a proxy.
|
| |
| |
| |
| |
| | |
In case none of the expired files could be deleted then it's a waste of
an API call to try to remove any of the metadata at all.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
deleted
If any of the expired files could not be deleted then we should not
forget about that, we should complain loudly and try again.
The code got this backwards and would have removed only the entries
referring to still existing files.
Test procedure:
1. Upload a file
2. chown root:root http_file_share/
3. In uploads.list, decrease 'when' enough to ensure expiry
4. Reload mod_http_file_share
5. Should see an error in the logs about failure to delete the file
6. Should see that the metadata in uploads.list is still there
7. chown http_file_share/ back to the previous owner
8. Reload mod_http_file_share
9. Should see logs about successful removal of expired file
10. Should see that the metadata in uploads.list is gone
11. Should see that the file was deleted
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
> "You can do anything in XMPP!"
> as a reminiscence of zombo.com
-- jonas’
> A study in simplicity.
Prosody tagline
|