Home / user-19511

Urda's questions

Martin Hope
Urda
Asked: 2014-10-30 14:16:45 +0800 CST
  • 2

I have a few exposed JSON scripts / programs for quick information gathering from a server. I use nginx to expose those as just raw urls. So given the following locations:

location ~ ^/api/status/? {
    rewrite ^(.*)$ /path/to/some/handler/wan.handler;
}

location ~ ^/api/status-lan/? {
    rewrite ^(.*)$ /path/to/some/handler/lan.handler;
}

Why does nginx match my status-lan call to the status location? So I can view my output from /api/status/ just fine, but if I view /api/status-lan/ I get the status location instead.

nginx
Martin Hope
Urda
Asked: 2012-02-07 05:47:27 +0800 CST
  • 1

Ok, so I have an Apache host I'm working on (shared host) who has this in their root .htaccess file.:

Options -Indexes

SSLOptions +StrictRequire

ErrorDocument 401 "<!DOCTYPE html><html lang='en'> ... "
ErrorDocument 403 "<!DOCTYPE html><html lang='en'> ... "

SSLRequireSSL

So when a user tries to connect without SSL, they are prompted with the custom 403 html listed in the file. This occurs while keeping their old URL in the address bar so they can just add the https quickly.

However, for error page improvements, it is desired to load a php file from ./error and use that file in the definition for ErrorDocument. Now this is the kicker, if one just specifies the document directly...

ErrorDocument 403 /error/script.php

They will get another 403 or Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. since the connection to the file is not under SSL. In an attempt to fix that, one may try this...

ErrorDocument 403 https://site.tld/error/script.php

But that redirects the client to https://site.tld/error/script.php which is UNDESIRED because they have to retype the url, and thus unable to just change the http to https.

So, I imagine I must do one of the following:

  • EXCLUDE ./error from the SSL requirement with some .htaccess handling OR
  • Build a REWRITE rule that detects the use of an error page, and doesn't rewrite the URL

I was unable to do either of this things yesterday. Perhaps neither of those options are viable, but I'm stuck at what to do.

How can I instruct .htaccess to allow http connections in ./error, or some other fix, so I still get my error pages, but the client still keeps their original URL?

apache-2.2 ssl .htaccess
Martin Hope
Urda
Asked: 2010-12-20 11:54:50 +0800 CST
  • 0

I have a simple hosting account, and the folder structure is as follows:

/ (web root)
|
|-domain1
|-domain2
|-domain3
|
...

Due to some server migrations going on, I needed to have a real domain pointed at the web root, let's say domain0.com with or without the www

I need an .htaccess file that forces all access to index.php page when you access http://domain0.com/ For example, you would be unable to render domain1's website by loading http://domain0.com/domain1/ and instead be forced to go to http://domain0.com/index.php

I have tried writing it on my own, but keep blowing up the server with bad redirects. Any help?

apache-2.2 .htaccess
Martin Hope
Urda
Asked: 2010-04-16 07:04:53 +0800 CST
  • 1

I'm running a Windows 2003 Dedicated server, and the box has been rock solid for more than 2 years now. Just recently, I have had an issue where after a certain ammount of time the server will just stop accepting connections on all ports except 80, and still responds to pings. If you surf to a static HTML page on the box, you can display it. If you pull up a PHP file that has an outside database connection, it fails. RDP refuses to connect, and LogMeIn reports that "The connection was reset"

The only fix at this time is to have the provider physically reboot my box to correct the issue. The event log doesn't seem to be leaving helpful messages, and I am at a lost to what is causing this error since I have not installed any new software in months on it.

Any tips or help would be appreciated to tracking down this issue. I don't mind updating the question as responses come in, I just do not know where to start troubleshooting because it seems random at this time.

Update:

Restarting WAMP does not correct the issue, nothing seems to be hogging memory at the time of the issue, and I am able to RDP into the box, to at least restart it (had it disabled). But connections out to MySQL databases, and FTP connections in or out fail. Connections over LogMeIn continue to fail. Is there anything I can use to trace this issue?

windows-server-2003-r2
Martin Hope
Urda
Asked: 2010-03-20 05:17:18 +0800 CST
  • 1

I am not sure how to do this, but I want to block all access to a specific set of folders on my web server. Say secret01 and secret 02...

homeDir
  |- data
  |- www
  |   |- .htaccess (file)
  |   |- images
  |   |- js
  |   |- secret01
  |   |- secret02
  |   |...
  |...

What rule(s) do I need to add to my root .htaccess file to do this? I want all access from the web blocked from going into these folders, period. Only way one could get to them would be over SFTP or SSH. So what rule am I looking for? I am preferably looking for a one-liner so I can add more folders or move it to another site down the road. I really would prefer if the rule could be placed in the .htaccess root file so I don't have to jump all over the place to lock and unlock folders.

= Update for Clarity =

I do not have access to the conf file for this host (it is in a shared environment) and I need to have these folders inside the webroot for a few shell purposes. If I could I would have already moved them up out of the webroot.

I also don't want to screw with the file permissions, just have a rule in my .htaccess that blocks web traffic from accessing a folder or set of folders.

security .htaccess blocking
Martin Hope
Urda
Asked: 2010-02-07 18:58:31 +0800 CST
  • 2

I am setting up a few PHP Gearman Daemons running on PEAR System_Daemon. I need them to be able to write to the following locations...

/var/run/{APPNAME}.pid
/etc/init.d/{APPNAME}
/gearman/log/{APPNAME}.log

What permissions should I set for them? I don't mind creating a different user or what have you, but I am just not the greatest with File Permissions. I want to do this right, not chmod 777 for ease of use and running as root which is never a good idea.

Help this file permission idiot?

linux php daemon file-permissions