On Fri, Nov 11, 2022 at 08:29:44AM -0500, blason wrote:
Hi there,
> By the way which one would you confirm is preferable method rewrite or
> return?
It depends, based on what you want to do.
For what I think you want, in this case, "return" is simpler.
f
--
Francis Dalyfran...
Thanks appreciate it. Will have to check and confirm.
By the way which one would you confirm is preferable method rewrite or
return?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,295715,295725#msg-295725
___
nginx mailing list -- nginx@ngi
On Thu, Nov 10, 2022 at 01:07:23PM -0500, blason wrote:
Hi there,
> I have a website http://web1.example.local/web1
> Instead I need a rewrite so that if user enters http://web1.example.local it
> will be diverted to http://web1.example.local/web1
If you want it to happen, without needing it to
Hi Team,
I am trying to write a below rewrite rule but somehow this is not working
and I would really appreicate if someone can help me on this?
I have a website http://web1.example.local/web1
Instead I need a rewrite so that if user enters http://web1.example.local it
will be diverted to http://
On Sun, Sep 11, 2016 at 08:12:00AM -0400, khav wrote:
Hi there,
> I am trying to make pretty urls using rewrite rules but they are not
> working
"Pretty urls" usually means that the browser *only* sees the original
url, and the internal mangling remains hidden.
A rewrite that leads to a HTTP r
I am trying to make pretty urls using rewrite rules but they are not
working
1.
https://example.com/s1/video.mp4 should be rewrite to
https://example.com/file/server/video.mp4
location = /s1/(.*)$ {
rewrite ^/s1/(.*) /file/server/$1 permanent;
}
2.
https://example.com/view/