change HTTP 301 body?

toine-ml · 2012-12-13T19:18:28+00:00

Hello! On Wed, Dec 12, 2012 at 8:29 AM, Brian Akins wrote: >> Running your business test suite (if any) against the latest devel >> version of n...

change HTTP 301 body?

toine-ml

Hello,

I've looked at RFC 2616 dealing with HTTP/1.1 and I've read this passage.

   The new permanent URI SHOULD be given by the Location field in the
   response. Unless the request method was HEAD, the entity of the
   response SHOULD contain a short hypertext note with a hyperlink to
   the new URI(s).

Do you know if it is possible to change the default 301 redirect body of
nginx/openresty (which currently looks like the following one) so that
it includes the hyperlink to the new URI ?

<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>ngx_openresty/1.2.1.14</center>
</body>
</html>


Thanks!
Antoine

agentzh

Hello!

On Thu, Dec 13, 2012 at 3:16 AM, Antoine wrote:
> Do you know if it is possible to change the default 301 redirect body of
> nginx/openresty (which currently looks like the following one) so that
> it includes the hyperlink to the new URI ?
>

Sure. Try this:

    ngx.status = 301
    ngx.header.location = new_url
    ngx.print(my_own_page)
    ngx.exit(301)

Best regards,
-agentzh

toine-ml

On 12/13/2012 08:01 PM, agentzh wrote:
> On Thu, Dec 13, 2012 at 3:16 AM, Antoine wrote:
>> Do you know if it is possible to change the default 301 redirect body of
>> nginx/openresty (which currently looks like the following one) so that
>> it includes the hyperlink to the new URI ?
>>
> 
> Sure. Try this:
>     ngx.status = 301
>     ngx.header.location = new_url
>     ngx.print(my_own_page)
>     ngx.exit(301)

Thanks agentzh,

I kept having problems on my side because I was using ngx.say somewhere
when getting my new location. Therefore, ngx.header.location eventually
contained a line break character at the end and I got curl error
messages like "Received problem 2 in the chunky parser".
But now that I found the origin of the "problem", I used ngx.print and
everything's all good :)

Could you just tell how much the performances are impacted when using
this kind of redirect instead of the built-in one (ngx.redirect)?

Have a good day,
Antoine

agentzh

Hello!

On Fri, Dec 28, 2012 at 2:30 AM, Antoine wrote:
>
> Could you just tell how much the performances are impacted when using
> this kind of redirect instead of the built-in one (ngx.redirect)?
>

The difference is extremely small and should be neglect-able :) On the
C level, they're essentially doing exactly the same operations.

Best regards,
-agentzh