#1104 Vcard errors on initial request for own vcard seem unhelpful
Reporter
Kevin Smith
Owner
Nobody
Created
Updated
Stars
★ (1)
Tags
Status-NeedInfo
Type-Defect
Priority-Medium
Kevin Smith
on
I haven't seen this myself, report from a Swift/Prosody user, but...
What steps will reproduce the problem?
1. Request own vcard before setting one
What is the expected output?
An empty vcard (example 4)
What do you see instead?
An item-not-found (example 3)
What version of the product are you using? On what operating system?
*shrug* :)
Please provide any additional information below.
54 isn't clear on when each should be used, but it seems unhelpful to return an error to the user when they request their own vcard - sending the empty reply seems appropriate.
(Found because Swift started showing vcard errors a year and some ago)
I haven't seen this myself, report from a Swift/Prosody user, but... What steps will reproduce the problem? 1. Request own vcard before setting one What is the expected output? An empty vcard (example 4) What do you see instead? An item-not-found (example 3) What version of the product are you using? On what operating system? *shrug* :) Please provide any additional information below. 54 isn't clear on when each should be used, but it seems unhelpful to return an error to the user when they request their own vcard - sending the empty reply seems appropriate. (Found because Swift started showing vcard errors a year and some ago)
Link to related mailing list discussion: https://mail.jabber.org/pipermail/standards/2018-March/034719.html
So what was the conclusion?
Changes