The client asks for the last

carriere.p — Tue, 18 Oct 2011 17:40:00 +0000

The client asks for the last nickname, which seems to be working well.

<iq type='get'>
    	<pubsub xmlns='http://jabber.org/protocol/pubsub'>
    		<items node='http://jabber.org/protocol/nick' max_items='1'/>
    	</pubsub>
    </iq>

The server replies with the last nickname, which is empty if no nickname exists :

<iq from='carriere.p@server' to='carriere.p@server/ressource' id='purplee9228bb7' type='result'>
	<pubsub xmlns='http://jabber.org/protocol/pubsub'>
		<items node='http://jabber.org/protocol/nick'>
			<item id='5259D99652540'>
				<nick xmlns='http://jabber.org/protocol/nick'>My Last Nickname</nick>
			</item>
		</items>
	</pubsub>
</iq>

The user changes his or her nickname using Pidgin's interface and send it. The client sends the new nickname :

<iq type='set' id='purplee9228bb8'>
	<pubsub xmlns='http://jabber.org/protocol/pubsub'>
		<publish node='http://jabber.org/protocol/nick'>
			<item>
				<nick xmlns='http://jabber.org/protocol/nick'>My New Nickname</nick>
			</item>
		</publish>
	</pubsub>
</iq>

When I tested 2.1.8, both on Windows Server 2003 and CentOS 6, those stanzas were working. The problem was that they weren't accepted on the server. Either by not sending a reply at all, or by sending the error I posted in the first post.

As I said, we are currently working with the 2.1.6 version, but as soon as I can, I'll install 2.1.9 on a test server and run some tests.

Thank you for your time!

Hi. It would be easier to

mfoss — Fri, 14 Oct 2011 09:34:23 +0000

Hi. It would be easier to reproduce the problem, if you showed what exact stanzas you send to set the nickname, and get it.

Also, if you are only interested in setting and asking nicknames, maybe you don't need pubsub: you can store nickname in vcards.

ejabberd - Comments for "[2.1.8] Publishing Forbidden on (...)protocol/nick"

The client asks for the last

Hi. It would be easier to