Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
There may many reasons. But I can find only these.
By creating vhost we maintain same file structure in the server.
We can have several server instance in one machine.
But are these really matter ? I doubt myself.
What is the difference between keep separate folder in localhost vs having separated vhost in localhost and deploying to the server.
Is there any other reasons to add(or are these not the reasons at all ?)
Thanks in advance.
Because your first point is the biggest reason.
If you have http://localhost/devel vs http://devel.local your relative pathing can get all screwed up
If you had a developer who wanted to make a home link they may do Home
This will redirect you to root folder on localhost and you wont end up where you should be
it is also a separation of concerns. If you do a vhost you know you are only within that project. Another thing is if say you had a .htaccess file in localhost, it would affect settings in your project folder if you did not override the .htaccess in your project folder
Another reason is subdomains, you cannot really mimic subdomains with folders without using a .htaccess, it is much easier with vhosts
You always want to mimic production as closely as possible otherwise you will run into bugs on production that you will spend minutes/hours/days debugging that you might not have run into if you would have mimiced the environment in the first place
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I am using hosting provided by 000webhost.com.
Root directory is: public_html
I set it's file attributes to 700 by using FileZilla ftp.
Also I set individual file permissions to 600.
public_html directory has only one file which is index.html.
Now even though I have set puclic permission to zero as evident from right-most zero in both 600 and 700. Still I am able to view file index.html by using web browser here is the link. Why is that? I thought last zero in 600 or 700 meant public would not be able to view file, what is happening now then?
Now, I think this is because the file is readable by your Apache user and it is Apache that is delivering the files to the browser. What is the ownership of the file/folder. Can you put these secure files outside the web root?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I got mail from Google Webmaster tools that strange URLs where indexed. URLs like mywebsite.com/cheap-medicine/, etc.
I have a Drupal website and I can see those URLs are indexed. And using proxy I can see the page myself. However, I cannot find the source.
I have looked into a bunch of files but they are unchanged.
Also I searched my entire database and of course looked into Drupal backend for strange content.
I even searched my entire server using Linux grep, also no result for words on the page. The database URL / routing tables also show no strange URLs.
I did of course also check .htaccess files
How are these URLs accessible if I cannot find them anywhere?
Look into your .htaccess file, it contains a lot of power. It can make these strange URIs mask themselves. Try to check the validity of that file. This might be where this is coming from.
If your .htaccess file, or any .htaccess file inside any subdirectory of the site weren't hacked on then you probably want to reinstall the Drupal core. If you followed proper development practice by never editing third party core files, then you will not lose any work or time, because it will be a fresh default copy of what you installed the first time.
After this, make sure core runs correctly in a default state, and that the problem is gone. Then you can copy back in your source files to your Drupal framework and reconfigure and resume.
If the problem comes back after you put your source files back, then the problem is in your sources.
You can also try grepping for the terms individually i.e. grep -rin "medicine" ./* on a GNU/Linux box to see if these terms show up.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
When making a php web site in dream weaver, does the site have to have htdocs folder ?
The problem I have is I have a domain www.whatever.com.
Once I created the index.php in dreamweaver, I hit the put button and it uploads just fine.
So the connection to my website from dreamweaver works.
But when I got to the website www.whatever.com , it shows an apache test page where I want the index.php to show.
The answer to your first question is "no". Every website functions differently and having a htdocs folder is not a requirement by any means.
I suggest trying to upload index.php to the root directory (folder). The "root" is basically the top level folder that you have access to on your hosting account. Then, if that doesn't work, keep trying folders until it does work. As other people suggested, the correct folder can be called "public", "public_html", "www" or something else.
Just be sure you remember where it is located for for future reference. And don't leave a bunch of index.php files scattered in various locations on your server or it could create problems on your website in the future.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have LAMP installed in my server and I use virtualhosts to map domains to subdirectories. I need to allow my customers to upload files (including php) to their server using FTP.
The problem is that a customer using a domain xxx.com.br uploaded a file test.php and executed it like:
xxx.com.br/test.php
The content of test.php if file_put_contents("../../xxx.txt","teste") and it worked! The file xxx.txt was created 2 levels above his domain folder! How do I prevent this from happening?
Don't give the PHP process access to directories it isn't meant to reach.
That's kind of the point of the whole permission system.
In Linux, PHP will generally run as its own user, just make sure that user doesn't have read or write permission to any files you don't want exposed.
For this purpose exists open_basedir configuration directive. More information about it for example here.
Moreover it is good to use FastCGI which allows each script to be run under its owner. More information about it for example here.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I've got WAMP server on my Windows machine (just starting to study Servers and what not so I'm new to all this).
What I want to know is how can I give Apache permission to access a folder, but users should not be able to access that folder.
I've got a folder containing images which anyone would be able to view if they knew the structure of my server's file system and directories. Therefore, what I wish to do is that this folder should be accessible by my .html and .php pages but not by a user who inputs the URL of the folder/image directly in their browser.
I realize this may not be possible, but there must be some alternative to what I'm trying to achieve. I'm very new to all this so I'd like to know if I'm going about this wrong way, whether I'm on the right track or if I simply need to edit my permissions in the httpd.conf file.
Unfortunately that's not possible. The way the browser loads images when they're referenced in your website is not different from the way it does load them when a user enters the same URL directly. SO you get either both or none.
What you CAN do is: disable indexing, so entering just the directory name without the image name results in an "Access Forbidden" error. For that, put this anywhere in your Apache config:
<Directory c:/path/to/your/directory>
Options -Indexes
</Directory>
(You may have to use Backslashes on Windows, not sure. Haven't done any Apache config on Windows fore some time. Can anybody help me out here?)
Another thing you can do is to write an PHP (or use any other server side language) script that reads those images and pases them to the browser. That way, you could check the referrer the browser sends and react to it. But I would not recommend this, as it yields more trouble than it solves, therefore I won't give you a ready made script for this.