Thanks everyone and sorry for the late reply here...due to OS upgrade from
IT team.
I tried using return directive to invoke the absolute URL and below case is
true :
-- if they are two different servers, then on the workspance one:
location = / { return 301 http://workspace.corp.no/workspace/age
On Mon, Jun 08, 2015 at 08:39:51AM -0400, smsmaddy1981 wrote:
Hi there,
> Yes, the absolute URL http://workspace.corp.no/workspace/agentLogin works
> fine
>
> I just need to understand the configuration approach to redirect the URL
> request (http://workspance) to absolute url
> (http://workspac
Yes, the absolute URL http://workspace.corp.no/workspace/agentLogin works
fine
I just need to understand the configuration approach to redirect the URL
request (http://workspance) to absolute url
(http://workspace.corp.no/workspace/agentLogin)
Posted at Nginx Forum:
http://forum.nginx.org/read.p
Does following line on work?location = /
{return 301
http://workspace.corp.no/workspace/agentLogin;}You need some web
server on to return a 301. Or you can try port
forwarding to Node-01, although IMHO, not a good idea.
At 2015-06-04 17:28:44, "smsm
Hi Francis
Expectation is to redirect the request to the absolute URL
(http://workspace.corp.no/workspace/agentLogin) when an end user access the
request http://
NGINX is installed on server Node-01
The content to be loaded (workspace-dns-name) is deployed on another server
Node-02
Steps to achi
On Tue, May 26, 2015 at 10:20:27AM -0400, smsmaddy1981 wrote:
Hi there,
>server {
>listen 80;
>server_name workspace.corp.no;
>
>location / {
> proxy_pass http://workspace.corp.no/workspace/agentLogin;
>}
> }
>
> Expected to see:
> accessing URL
Thanks for the response #Vikrant and #Valentin
Below are the issue details:
What I have Configured:
server {
listen 80;
server_name workspace.corp.no;
location / {
proxy_pass http://workspace.corp.no/workspace/agentLogin;
}
}
Expected to see:
access
On Thursday 21 May 2015 18:52:25 smsmaddy1981 wrote:
> Can somebody answer my query pls.?
>
You're probably right about the proxying loop, but there's no
way to answer your question until you provide some information.
It's always a good idea to start any question with providing output
of "nginx
First thing I would have done is to check max open file limit in system
where I am getting it error.
YOu can check that by "ulimit -a" command. If it is very low then
increasing it might fix it.
Alternatively you can try playing with config NGINX
http://wiki.nginx.org/CoreModule#worker_rlimit_nofi
Can somebody answer my query pls.?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,258982,259050#msg-259050
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi Talents,
Need your support immediately on the below requirement:
I have configure DNS "worsktream.com" to proxy pass the complete URL
"http://worsktream.com/workstream/agentLogin";
while invoking the dns name following message is thrown:
- error 414 Request-URI Too Large
And after config
11 matches
Mail list logo
