Test and document X-Priority in header whitelist (Trac #1494)

[str4d]

priority can be a useful flag and it has no anonymity implications. As headers are encrypted only receiver sees it if set. And update documentation that priority flag is allowed

Migrated from https://trac.i2p2.de/ticket/1494

{
    "status": "infoneeded_new", 
    "changetime": "2015-08-05T01:54:40", 
    "description": "priority can be a useful flag and it has no anonymity implications.\nAs headers are encrypted only receiver sees it if set.\nAnd update documentation that priority flag is allowed", 
    "reporter": "user", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1438739680589550", 
    "component": "apps/plugins", 
    "summary": "I2P-Bote: allow priority in header", 
    "priority": "trivial", 
    "keywords": "I2P-Bote", 
    "version": "0.9.18", 
    "parents": "", 
    "time": "2015-03-19T20:49:55", 
    "milestone": "undecided", 
    "owner": "", 
    "type": "defect"
}

[str4d]

Trac update at 20150723T04:44:03:

• str4d commented:

X-Priority has been in the header whitelist since at least 2010, probably earlier.

What exactly is it that you want, or are having problems doing?

• str4d changed status from "new" to "infoneeded_new"

[str4d]

Trac update at 20150726T16:20:01:

• user commented:

it didn't work for me for some reason. But as it is there, all that's missing is that documentation mention it too, as otherwise docs are wrong saying when they mention what the only things are that get sent and do not include the X-Priority header.

Then this can be closed. Thx

• user changed status from "infoneeded_new" to "new"

[str4d]

Trac update at 20150805T01:54:40:

• str4d commented:

Replying to [comment:2 user]:

it didn't work for me for some reason. But as it is there, all that's missing is that documentation mention it too, as otherwise docs are wrong saying when they mention what the only things are that get sent and do not include the X-Priority header.

Can you point to where the docs are wrong? Thanks.

• str4d changed status from "new" to "infoneeded_new"