Trailing Slash redirection poblem
Muhammad Yousuf Khan
sirtcp at gmail.com
Mon May 2 12:48:12 UTC 2016
first of all my apologies if i question something inapplicable , this
could be the result of my less knowledge in nginx. i hope you guys don't
Thanks for the reply, actually we have 5 categories. and then we have
hundred plus post in each category. now when user click on our category. he
sees intro about the category and then list of all posts.
when user click on catagory it open up like this
and when post is clicked it opens up like this
but now what client want is when some one open up the category it should
open up like this.
https://xxxx.com/catagory (with out trailing slash)
This is all what they want.
On Mon, May 2, 2016 at 2:18 PM, Francis Daly <francis at daoine.org> wrote:
> On Sun, May 01, 2016 at 01:16:51PM +0500, Muhammad Yousuf Khan wrote:
> Hi there,
> > >>The configuration you have shown says "if the request is for /live/,
> > >>ask the browser to instead request /live".
> > >>The configuration you have not shown says "if the request is for /live,
> > >>ask the browser to instead request /live/".
> > Thanks for the tip I think I got the problem but could not resolve it.
> If you make the request for "/live", what response do you actually want?
> The contents of some file? The output of wordpress being given some
> arguments? Be as specific as possible, and it is much more likely that
> you will understand how nginx needs to be configured to do that.
> > >>So: why do you want to remove the trailing slash, in the shown
> > >>configuration?
> > Actually this is a requirement from my client.
> Sometimes, the correct response to a client requirement is "no".
> It is not yet clear to me whether this is one of those times.
> Francis Daly francis at daoine.org
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx