Software /
code /
prosody-modules
File
mod_post_msg/sendxmpp-curl.sh @ 6199:fe8222112cf4
mod_conversejs: Serve base app at /
This makes things slightly less awkward for the browser to figure out which
URLs belong to a PWA. The app's "start URL" was previously without the '/' and
therefore was not considered within the scope of the PWA. Now the canonical
app URL will always have a '/'.
Prosody/mod_http should take care of redirecting existing links without the
trailing / to the new URL.
If you have an installation at https://prosody/conversejs then it is now at
https://prosody/conversejs/ (the first URL will now redirect to the second
URL if you use it).
The alternative would be to make the PWA scope include the parent, i.e.
the whole of https://prosody/ in this case. This might get messy if other
PWAs are provided by the same site or Prosody installation, however.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Tue, 11 Feb 2025 13:18:38 +0000 |
parent | 4524:9764d27db681 |
line wrap: on
line source
#!/bin/bash # Does HTTP POST compatible with mod_post_msg for prosody # Aims to be compatible with sendxmpp syntax # API: # http://host/msg/user => msg to user@host # or http://whatever/msg/user@host => same # HTTP Basic auth # sendxmpp # $0 [options] <recipient> test -f $HOME/.sendxmpprc && read username password < $HOME/.sendxmpprc TEMP="$(getopt -o f:u:p:j:o:r:tlcs:m:iwvhd -l file:,username:,password:,jserver:,component:,resource:,tls,headline,message-type:,chatroom,subject:,message:,interactive,raw,verbose,help,usage,debug -n "${0%%*/}" -- "$@" )" if [ $? != 0 ] ; then echo "Terminating..." >&2 ; exit 1 ; fi eval set -- "$TEMP" while true; do case "$1" in -f|--file) read username password < "$2"; shift 2;; -u|--username) username="$2"; shift 2;; -p|--password) password="$2"; shift 2;; -j|--jserver) server="$2"; shift 2;; -m|--message) message="$2"; shift 2;; -v|--verbose) verbose="yes"; shift;; -i|--interactive) interactive="yes"; shift;; # multiple messages, one per line on stdin -r|--resource) resource="$OPTARG"; shift 2;; # not used -h|--help|--usage) echo "usage: ${0##*/} [options] <recipient>" echo "or refer to the the source code ;)"; exit;; --) shift ; break ;; *) echo "option $1 is not implemented" >&1; shift ;; # TODO stuff # FIXME the above will fail if the opt has a param esac done if [ $# -gt 1 ]; then echo "multile recipients not implemented" >&1 # TODO stuff exit 1 fi # Can be user@host or just user, in wich case the http host is used recipient="$1" shift if [ -z "$server" ]; then server="${username#*@}:5280" fi if [ -z "$recipient" -o -z "$server" -o -z "$username" ]; then echo "required parameter missing or empty" >&1 exit 1 fi do_send() { #echo \ curl "http${secure:+s}://$server/msg/$recipient" \ -s ${verbose:+-v} \ -u "$username${password:+:$password}" \ "$@" } send_text() { do_send -H "Content-Type: text/plain" "$@" } if [ -z "$interactive" ]; then send_text -d "${message:-@-}" else while read line; do send_text -d "$line" done fi # TODO single curl line