Return-Path: 
 <modules-dev-return-3926-apmail-httpd-modules-dev-archive=httpd.apache.org@httpd.apache.org>
X-Original-To: apmail-httpd-modules-dev-archive@minotaur.apache.org
Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 0B27D909B
	for <apmail-httpd-modules-dev-archive@minotaur.apache.org>;
 Mon, 18 Jun 2012 12:53:17 +0000 (UTC)
Received: (qmail 2287 invoked by uid 500); 18 Jun 2012 12:53:16 -0000
Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org
Received: (qmail 1775 invoked by uid 500); 18 Jun 2012 12:53:12 -0000
Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:modules-dev-help@httpd.apache.org>
List-Unsubscribe: <mailto:modules-dev-unsubscribe@httpd.apache.org>
List-Post: <mailto:modules-dev@httpd.apache.org>
List-Id: <modules-dev.httpd.apache.org>
Reply-To: modules-dev@httpd.apache.org
Delivered-To: mailing list modules-dev@httpd.apache.org
Received: (qmail 1745 invoked by uid 99); 18 Jun 2012 12:53:11 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jun 2012 12:53:11 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of info@bnoordhuis.nl designates
 209.85.160.45 as permitted sender)
Received: from [209.85.160.45] (HELO mail-pb0-f45.google.com) (209.85.160.45)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jun 2012 12:53:03 +0000
Received: by pbbro12 with SMTP id ro12so9606483pbb.18
        for <modules-dev@httpd.apache.org>;
 Mon, 18 Jun 2012 05:52:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:x-originating-ip:in-reply-to:references:date
         :message-id:subject:from:to:content-type:x-gm-message-state;
        bh=cbXdksl397hr577lhMHUiY+JVGrdPGO5MKYQDGZ5U6Y=;
        b=A9h/1FiQn5Pu0Jcr4U9zm8o+MAuYJctFVr0H+w/8zAMmRWwiUb2E5Xu5B7eGFfC5My
         D3cj5wO8oxhp5F5dZXBxIZSrjksDFhzxrinKcVtpyLxRZ0onVtVbyccEqrF6/nb/wwa+
         iCWnkSLMbyJ/E6OoB71Szhi78qjIf6g8LIsKUBWMloR7e8eXFcXl3BIHq+s8EkYWcJsl
         4X0R2NUc0uWUb+WPaNp11rFaSCz+meefY/AsWQuUiwcNKV52r8y22UVzNVIzV/Y7Rk8o
         ttgKgL+ae6ydKQNsHtaBgpqFOjqpIqxEnY29wTiwpxfmYNFmZUUK1iMkBENq2Z6k00Kq
         PndA==
MIME-Version: 1.0
Received: by 10.68.221.10 with SMTP id qa10mr50136247pbc.154.1340023961709;
 Mon, 18 Jun 2012 05:52:41 -0700 (PDT)
Received: by 10.68.241.196 with HTTP; Mon, 18 Jun 2012 05:52:41 -0700 (PDT)
X-Originating-IP: [87.214.96.125]
In-Reply-To: <20120618025345.4OPSJ.127270.root@eastrmwml105>
References: 
 <CAHQurc_9wrOS-r_NTOTAKit3do1M4v+0G55JwM3ONkE39GB14Q@mail.gmail.com>
	<20120618025345.4OPSJ.127270.root@eastrmwml105>
Date: Mon, 18 Jun 2012 14:52:41 +0200
Message-ID: 
 <CAHQurc_GBXeB2S9jV_R8cW2yU1nox_-n1h616zYX4fce4rWoLA@mail.gmail.com>
Subject: Re: How to access client certificate PEM and incoming request headers
 in a module?
From: Ben Noordhuis <info@bnoordhuis.nl>
To: modules-dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: 
 ALoCoQnJF2BKMyQmNsA5olg4LHtslakP7QyFobL4Fvcdnb5xYVzz7Kxj8WlWgmm8RYuwE7w4Nc11
X-Virus-Checked: Checked by ClamAV on apache.org

On Mon, Jun 18, 2012 at 8:53 AM,  <ohaya@cox.net> wrote:
> I added a call to header_request_env_var(r, "REMOTE_URI"), just to see what it got (running Apache in single-process mode):
>
> printf("REMOTE_URI=[%s]\n", header_request_env_var(r, "REMOTE_URI") );
>
> Then I pointed a browser to http://<myhost>/test, where /test was a <Location> with a RequestHeader (to trigger mod_headers) but I got:
>
> REMOTE_URI=[(null)]
>
> Shouldn't that be showing:
>
> REMOTE_URI=[/test]
>
> ??

Did you mean REMOTE_USER or REQUEST_URI? I don't think there's such a
thing as REMOTE_URI.