# How to view Nginx wiki history?

**URL:** <https://www.ruby-forum.com/t/how-to-view-nginx-wiki-history/224211>\
**Category:** NGINX\
**Created:** [November 3, 2012, 7:09am UTC](https://www.ruby-forum.com/t/how-to-view-nginx-wiki-history/224211 "2012-11-03T07:09:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![aris](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/258eb7/32.png) [@aris](https://www.ruby-forum.com/u/aris)\
**Post date:** [November 3, 2012, 7:09am UTC](https://www.ruby-forum.com/t/how-to-view-nginx-wiki-history/224211/1 "2012-11-03T07:09:19Z")

</div>

For example, this page: [http://wiki.nginx.org/WordPress](http://wiki.nginx.org/WordPress)

In the Google cache:  
[http://webcache.googleusercontent.com/search?q=cache:\_fqHWtIaxmsJ:wiki.nginx.org/WordPress+&cd=1&hl=zh-CN&ct=clnk](http://webcache.googleusercontent.com/search?q=cache:_fqHWtIaxmsJ:wiki.nginx.org/WordPress+&cd=1&hl=zh-CN&ct=clnk)

It contains the following lines:

> > # include the “?$args” part so non-default permalinks doesn’t break

when using query string try\_files $uri $uri/ /index.php?$args;

> > try\_files $uri $uri/ /index.php?$args;

But it was removed in the latest version of wiki:  
[http://wiki.nginx.org/WordPress](http://wiki.nginx.org/WordPress)

Sometimes we want to know why they are changed, and when they have  
removed.  
Anyone mind to explain?

---

<div class="post-metadata">

**Author:** ![howard\_chen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/bbce88/32.png) [@howard\_chen](https://www.ruby-forum.com/u/howard_chen)\
**Post date:** [November 4, 2012, 2:58pm UTC](https://www.ruby-forum.com/t/how-to-view-nginx-wiki-history/224211/2 "2012-11-04T14:58:40Z")

</div>

On Saturday 03 November 2012 10:08:48 howard chen wrote:

> Re: How to view Nginx wiki history?

You should register an account to view the history:

> **[GitHub - nginxinc/nginx-wiki: ARCHIVED -- Source for the now archived NGINX Wiki...](https://github.com/nginxinc/nginx-wiki)**
>
> ARCHIVED -- Source for the now archived NGINX Wiki section of https://www.nginx.com

wbr, Valentin V. Bartenev

–

> **[F5 NGINX: Built for cloud-native apps. Ready for AI traffic.](https://www.f5.com/products/nginx)**
>
> Deliver modern applications with NGINX. Explore high-performance load balancing, API gateways, and web server solutions trusted by top global enterprises.

> **[nginx: donation](http://nginx.org/en/donation.html)**

---

<div class="post-metadata">

**Author:** ![howard\_chen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/bbce88/32.png) [@howard\_chen](https://www.ruby-forum.com/u/howard_chen)\
**Post date:** [November 4, 2012, 3:08pm UTC](https://www.ruby-forum.com/t/how-to-view-nginx-wiki-history/224211/3 "2012-11-04T15:08:01Z")

</div>

On 4 November 2012 13:57, Valentin V. Bartenev [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> On Saturday 03 November 2012 10:08:48 howard chen wrote:
> 
> > Re: How to view Nginx wiki history?
> 
> You should register an account to view the history:  
> [GitHub - nginxinc/nginx-wiki: ARCHIVED -- Source for the now archived NGINX Wiki section of https://www.nginx.com · GitHub](http://wiki.nginx.org/index.php?title=Special:UserLogin)

That really sucks. Can it be configured differently to allow  
non-authenticated users access to page histories?

As we’re on the topic of historic documentation across a versioned  
piece of software like nginx, I’d like to put in a plea here for  
something to be worked out to expose the mapping of config directives  
to the version in which they were introduced, or when their behaviours  
changed - in a _structured_ format.

IMHO that’s a really major documentation flaw in both the wiki and the  
official documentation, as the inline notes about version  
applicability are both sparse and not formalised/structured at all  
usefully.

## Jonathan

Jonathan M. // Oxford, London, UK

> **[Jonathan Matthews :: Words Typed, Great Rates For Cash](https://www.jpluscplusm.com)**

---

<div class="post-metadata">

**Author:** ![howard\_chen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/bbce88/32.png) [@howard\_chen](https://www.ruby-forum.com/u/howard_chen)\
**Post date:** [November 9, 2012, 4:09am UTC](https://www.ruby-forum.com/t/how-to-view-nginx-wiki-history/224211/4 "2012-11-09T04:09:36Z")

</div>

Hello!

On Sun, Nov 04, 2012 at 02:07:32PM +0000, Jonathan M. wrote:

> On 4 November 2012 13:57, Valentin V. Bartenev [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:
> 
> > On Saturday 03 November 2012 10:08:48 howard chen wrote:
> > 
> > > Re: How to view Nginx wiki history?
> > 
> > You should register an account to view the history:  
> > [GitHub - nginxinc/nginx-wiki: ARCHIVED -- Source for the now archived NGINX Wiki section of https://www.nginx.com · GitHub](http://wiki.nginx.org/index.php?title=Special:UserLogin)
> 
> That really sucks. Can it be configured differently to allow  
> non-authenticated users access to page histories?

Non-authenticated users actually have access, but there is no link  
provided. E.g.

> **[GitHub - nginxinc/nginx-wiki: ARCHIVED -- Source for the now archived NGINX Wiki...](https://github.com/nginxinc/nginx-wiki)**
>
> ARCHIVED -- Source for the now archived NGINX Wiki section of https://www.nginx.com

> As we’re on the topic of historic documentation across a versioned  
> piece of software like nginx, I’d like to put in a plea here for  
> something to be worked out to expose the mapping of config directives  
> to the version in which they were introduced, or when their behaviours  
> changed - in a _structured_ format.
> 
> IMHO that’s a really major documentation flaw in both the wiki and the  
> official documentation, as the inline notes about version  
> applicability are both sparse and not formalised/structured at all  
> usefully.

In official documentation we’ve introduced formal   
tag, e.g.

[http://trac.nginx.org/nginx/browser/nginx\_org/xml/en/docs/http/ngx\_http\_ssl\_module.xml#L219](http://trac.nginx.org/nginx/browser/nginx_org/xml/en/docs/http/ngx_http_ssl_module.xml#L219)

Though in more or less nontrivial cases like new directive  
parameters and so on - inline notes are unavoidable.

–  
Maxim D.

> **[F5 NGINX: Built for cloud-native apps. Ready for AI traffic.](https://www.f5.com/products/nginx)**
>
> Deliver modern applications with NGINX. Explore high-performance load balancing, API gateways, and web server solutions trusted by top global enterprises.
