#1104 Vcard errors on initial request for own vcard seem unhelpful

Reporter Kevin Smith
Owner Nobody
Stars ★ (1)
  • Status-WontFix
  • Priority-Medium
  • Type-Defect
  1. 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)

  2. MattJ on

    Link to related mailing list discussion: https://mail.jabber.org/pipermail/standards/2018-March/034719.html

  3. Zash on

    So what was the conclusion?

    • tags Status-NeedInfo
  4. Zash on

    From my reading of the lost archives, both item-not-found and empty vcard mean the exact same thing and thus clients should handle it the same, thus no action need be taken here. I observe that mod_vcard_legacy behaves differently, as it composes a legacy vcard(-temp) from various PEP nodes, and all of those being empty or inaccessible will result in an empty vcard returned. Personally I would recommend moving towards vcard4 if more advanced user profiles are needed.

    • tags Status-WontFix

New comment

Not published. Used for spam prevention and optional update notifications.