1

Closed

Invalid headers?

description

In the version 24 headers I see
 
(a) X-Newseader header:
 
X-Newsreader: Community Forums NNTP Server 1.1.24.0
 
This does not seem correct to me. As far as the client is concerned, the bridge is a server, not a newsreader.
 
(b) References header:
 
For an original post I see empty References header. Shouldn't it be absent?
Closed Jun 5, 2010 at 2:20 PM by
Starting with V28, also X-Newsreader is used to identify the client newsreader.

comments

jkalmbach wrote Jun 3, 2010 at 4:57 PM

a: WHAT do you expect? Is there a standard of naming a X-Newsreader?
b: Is fixed in the next release (V26)

davewilk wrote Jun 3, 2010 at 8:12 PM

Jochen:

(a) I don't know. Maybe you need to invent your own. X-NNTP-Server perhaps?

For me, X-Newsreader is the client reader that actually generated the message, but for the forums this information is lost (and the message may have been created directly on the forums).

jkalmbach wrote Jun 3, 2010 at 9:41 PM

The feature request for the web-service is:
Add an "X-Newsreader" to each aricle; so we could identify on which channel this message was generated (for example, via (which) Bridge (and newsreader) or Web-Forums)

davewilk wrote Jun 4, 2010 at 9:07 AM

Jochen:

I think it is good that the bridge, and its version number, are mentioned in the headers. I just don't think you should use X-NewsReader for it, that's all.

As to the feature request for the web service, that's fine, but I think there are more important things.

jkalmbach wrote Jun 4, 2010 at 1:00 PM

Hi David,
I will now do the following:
If the cleint is posting an article via my bridge, then I will emit a "
This anchior is not seen in the normal forum; only if you edit an entry, you will see the anchor.

And if a client uses my bridge, it will search for such a anchor and retrive the user-agent from this line and emit it as "X-Newsreader".

Would that be ok?

jkalmbach wrote Jun 4, 2010 at 1:00 PM

I am unable to get the "origin" of the message, so I will continue to use the bridge as the origin of the message. I will also make a note, that the webservice should return the orogin of the message.


** Closed by jkalmbach 03.06.2010 14:39

jkalmbach wrote Jun 4, 2010 at 1:00 PM

Hi David,
I will now do the following:
If the cleint is posting an article via my bridge, then I will emit a "
This anchior is not seen in the normal forum; only if you edit an entry, you will see the anchor.

And if a client uses my bridge, it will search for such a anchor and retrive the user-agent from this line and emit it as "X-Newsreader".

Would that be ok?

davewilk wrote Jun 4, 2010 at 3:18 PM

Jochen:

It's OK, but I'm not sure it's working quite right.

Am I correct in thinking that this only works if I use the PlainText Converter?

I don't currently use it (because I have my own client-side converter), and I am seeing both

X-NNTP-Server: Community Forums NNTP Server 1.1.27.0
X-Newsreader: Community Forums NNTP Server 1.1.27.0

Shouldn't the second one be missing?

[This idea of feeding information through HTML tags had occurred to me also, but I thought you might disapprove of it, which I do slightly :-).]

jkalmbach wrote Jun 4, 2010 at 3:44 PM

It should work in any case (not only for PlainTextConverter). BUT your newsreader must post a "User-Agent" string. And you will also only see this, if you retrieve your posted article again from the server.

davewilk wrote Jun 4, 2010 at 4:18 PM

Hi Jochen:

Ah yes, it works if I specify the User-Agent string (see my "UserAgent test" theread in msdnsandbox). Neat!!

I still think X-Newsreader should be absent if there was no User-Agent specified.

Also, I think, most readers do not provide User-Agent string; they use X-Newsreader. So maybe you need to look for both.

jkalmbach wrote Jun 4, 2010 at 4:37 PM

It should now work with V28 also with X-Newsreader...