Re: [websec] X-Requested-With header field
Tobias Gondrom <tobias.gondrom@gondrom.org> Wed, 14 December 2011 04:58 UTC
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A50411E8080 for <websec@ietfa.amsl.com>; Tue, 13 Dec 2011 20:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.003
X-Spam-Level:
X-Spam-Status: No, score=-96.003 tagged_above=-999 required=5 tests=[AWL=0.775, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6YgchaflNcc for <websec@ietfa.amsl.com>; Tue, 13 Dec 2011 20:58:15 -0800 (PST)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (www.gondrom.org [83.169.7.107]) by ietfa.amsl.com (Postfix) with ESMTP id 5AC9121F84F5 for <websec@ietf.org>; Tue, 13 Dec 2011 20:58:15 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gondrom.org; b=s+hv1sNiHRWxXbfCq99KlPyk5FUVVde2fYME/9Ik1nLglmJa1tmy1wz1rfcT2vRF8DJqNV+WuRpKpWFev9W9pKQnPSk/iij2iv3v7N5qb92xNQ5cft6JVRZyij1Yf3l4; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
Received: (qmail 1828 invoked from network); 14 Dec 2011 05:57:54 +0100
Received: from unknown (HELO ?10.5.8.213?) (61.8.220.69) by www.gondrom.org with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Dec 2011 05:57:54 +0100
Message-ID: <4EE82CCF.1090606@gondrom.org>
Date: Wed, 14 Dec 2011 04:57:51 +0000
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111110 Thunderbird/8.0
MIME-Version: 1.0
To: websec@ietf.org
References: <4EE727C4.3020606@gmx.de> <4EE771DC.7050600@stpeter.im>
In-Reply-To: <4EE771DC.7050600@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [websec] X-Requested-With header field
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/websec>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Dec 2011 04:58:16 -0000
Maybe two questions: 1. any volunteers to write this up? 2. is there a coherent documentation of expected use of the header? I looked a bit, but didn't find a good one. Best regards, Tobias On 13/12/11 15:40, Peter Saint-Andre wrote: > On 12/13/11 3:24 AM, Julian Reschke wrote: > >> it seems this header field is widely implemented. Is it here to stay? If >> so, shouldn't it be documented somewhere? > +1, even if it does start with that ugly "X-" string. :) > > _______________________________________________ > websec mailing list > websec@ietf.org > https://www.ietf.org/mailman/listinfo/websec
- Re: [websec] X-Requested-With header field Peter Saint-Andre
- Re: [websec] X-Requested-With header field Tobias Gondrom
- [websec] X-Requested-With header field Julian Reschke