view mod_pubsub_get/README.md @ 6319:04c3273cb81f

mod_auth_cyrus: Add empty 'profile' table to SASL handler objects This is for compatibility with Prosody's built-in util.sasl objects. A SASL profile table usually includes methods supported by the backend, which can be used by SASL mechanism handlers to perform operations (such as testing the password). It also optionally contains a 'cb' field with channel binding method handlers. The Cyrus backend doesn't support channel binding, and doesn't have the same concept of auth backend methods (it handles all that internally, and Prosody has no insight or control over it). Thus, we create an empty profile which informs Prosody that the SASL handler does not support any of the auth or channel binding methods. Some features will not work, but they didn't work anyway. This just makes it explicit. This fixes a traceback in mod_sasl2_fast, which expected SASL handlers to always contain a 'profile' field.
author Matthew Wild <mwild1@gmail.com>
date Thu, 04 Sep 2025 10:14:46 +0100
parents 119c0eb65bf3
children
line wrap: on
line source

---
labels:
    - "Stage-Alpha"
summary: Get pubsub items via HTTP GET
---

# Introduction

WARNING: this module does not implement any type of access control and will effectively make all
pubsub data public on the component it is loaded onto.

This module lets you fetch the items of a specific pubsub node via an HTTP GET request.
I implemented it for a read-only view of comments published according to XEP-0277.

# Configuration

Nothing is configurable, just load the module on a specific component.

```lua
Component "comments.example.com" "pubsub"
    modules_enabled = { "pubsub_get" }
```

# Use

To query the items of the node "urn:xmpp:microblog:0:comments/some-article", issue a GET for
`https://comments.example.com:5281/pubsub_get?node=urn:xmpp:microblog:0:comments/some-article`.
This will return a JSON object containing the items data.

# TODO

-   Only return items with "open" access model

# Compatibility

Requires Prosody trunk / 0.12