httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexei Kosut <ako...@organic.com>
Subject Re: inneresting behavior
Date Tue, 18 Jun 1996 17:18:58 GMT
On Tue, 18 Jun 1996, Rob Hartill wrote:

> It looks like something easy to add.

It is.

> Is a HTTP/1.0 response containing Content-location: allowed?

Sure. A HTTP/1.0 message can contain anything it wants to :)

> It's worth adding on the off-chance that it'll get used by some
> browsers. It needs to be implemented so that scripts can override
> it (no merged/duplicated headers).

It's probably worth adding. Just not now. Let's get 1.1.0 out.

> Anyone feel like doing it?

The following (untested) patch should do the trick:

Index: http_request.c
===================================================================
RCS file: /export/home/cvs/apache/src/http_request.c,v
retrieving revision 1.10
diff -c -r1.10 http_request.c
*** http_request.c	1996/06/17 20:28:19	1.10
--- http_request.c	1996/06/18 17:18:38
***************
*** 841,846 ****
--- 841,850 ----
  				  * about this, don't change 'em back!
  				  */
  
+     /* If there isn't already one, generate a Content-Location */
+     if (!table_get(new->err_headers_out, "Content-Location"))
+       table_set(new->headers_out, "Content-Location", new->uri);
+ 
      sprintf (t, "%d", r->status);
      table_set (new->subprocess_env, "REDIRECT_STATUS", pstrdup (r->pool, t));
  


-- Alexei Kosut <akosut@organic.com> 
   http://www.nueva.pvt.k12.ca.us/~akosut/






Mime
View raw message