The com.apple.quarantine extended attributes probably have nothing to do with the issues you are having with Apache. They are part of the file quarantine feature that was added in 10.5:
File Quarantine is a new feature in Leopard designed to protect users from trojan horse attacks. It allows applications which download file content from the Internet to ...
OS X provides launchctl to control which daemons are started at boot time.
To stop and disable Apache:
Type the following command (type your login password when sudo requests it):
sudo launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist
A few words on launchctl's -w option
The -w option is the silver bullet for ...
There is an updated tutorial here: How to Set up Apache in macOS Sierra 10.12
It includes extra configurations like uncommenting the following lines by removing the "#":
#LoadModule userdir_module libexec/apache2/mod_userdir.so
#LoadModule vhost_alias_module libexec/apache2/mod_vhost_alias.so
The file /etc/apache2/original/httpd.conf (in OS X 10.11.5) has the following content with three trailing empty lines:
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
# In particular, ...
It looks like you have nearly everything correct. I'm running Mavericks with a couple dozen virtual hosts, so this should work for you.
First, and this might be all you need to do to fix things, you need to enclose your DocumentRoot in quotes. So,
There's a number of options for doing this, but the easiest way is to just use your Login Items. More specifically:
In the Finder, press CommandK (or click on the Go menu and select Connect to Server...)
Now enter the server address
Click on the Connect button
IMPORTANT: If you're a registered user, when entering your login details you must ensure you ...
I think default apache path
and homebrew apache path
And you may have 2 apache in your system use this cmd to check
which -a apachectl
apache for default
apache for homebrew. I think so.
The command below use for default apache. I think.
It is using postfix. At a high-level, when you execute the mail command, the following is happening:
Invoking mail drops your message as a file in the postfix maildrop directory, i.e., /var/spool/postfix/maildrop. This happens because mail calls sendmail which calls postdrop which puts the file in the maildrop.
The postfix main daemon, master is configured ...
Okay, I ended up running
$ sudo apachectl configtest
httpd: Syntax error on line 488 of /usr/local/etc/apache2/2.2/httpd.conf: Cannot load /usr/local/Cellar/php56/5.6.14/libexec/apache2/libphp5.so into server: dlopen(/usr/local/Cellar/php56/5.6.14/libexec/apache2/libphp5.so, 10): image not found
When I edited httpd.conf, it turned out that ...
As has been pointed out already, unless you are specifically forwarding http traffic from your router to your machine, your locally hosted stuff will only be available to you and the other computers on your local network.
To answer your question on restricting access to your webserver to just your machine. You can do this a couple of ways.
First, make sure you are looking at the right apache config. Base OS X includes a config file, but the one used in Server is at /Library/Server/Web/Config/apache2/sites.
The two lines that makes Xcode the default is in 0000_any_80_.conf:
DirectoryIndex index.html index.php /xcode/ /wiki/ default.html
You can do this with the OS X Server app.
Go to the Websites service.
Double-click your server website in the list.
Click Edit… for Index Files.
Delete /xcode/ from the list.
Click OK on both boxes and wait for the service to update.
Then Xcode will only be accessible from host.name.tld/xcode
Your dnsmasq daemon isn't properly configured.
Your external resolver is working: all queries to non-dev hosts/domains are forwarded to 3rd-party DNS servers with the resolv-file=/usr/local/etc/resolv-dnsmasq.conf line - in your case the configured file contains two public Google DNS servers.
Your internal resolver doesn't resolve internal names though.
First check name resolution with the system resolver:
dscacheutil -q host -a name localhost
If you get an output like:
the system resolver works correctly.
Stop your node.js app, create a simple node.js server by using this file with an arbitrary name (e.g. multiserver.js):
I had the same problem on a Sierra system. I run:
which -a apachectl
to stop the apache by apple version: sudo /usr/sbin/apachectl stop
To see the running processes: ps aux | grep httpd Outputted:
ibook 1359 0,0 0,0 2432804 768 s000 S+ 4:13pm 0:00.00 grep httpd
Yes, Apple's Swift language can be used to create a web server that accepts HTTPS connections. See Going Server-side with Swift Open Source for Apple's introduction to developing servers.
Using Swift, you have access to a range of included and third party SSL/TLS libraries. The language used to write the library is not important, so long as the library ...
OS X actually has (at least) 3 firewalls. Since you've turned off the application firewall (in System Preferences -> Security & Privacy -> Firewall) and checked the Berkeley packet filter (pfctl -sa), I'm guessing it's the old ipfw that's doing the blocking. You can check with sudo ipfw show -- that'll list the active rules, along with counts of how many ...
You have to run as root to bind to the privileged ports (<1024). You can run Mongoose via sudo, but then you will have a web server running as root. Not a good idea!
Changing user with run_as_user parameter also seems to be unsupported on Mac:
Mongoose[22361:507] The application with bundle ID (null) is running setugid(),
which is not allowed.
Like on Sierra vhosts seem to need to be activated
sudo vi /etc/apache2/httpd.conf
and uncomment the following lines by removing the hashtag (#)
.#LoadModule vhost_alias_module libexec/apache2/mod_vhost_alias.so
sudo apachectl restart
and you'll be good to go
In both scenarios, using the IP or machinename.local address of the Mac will only give you the default website on that Mac. Your web apps are all at the top-level so Nginx is expecting different hostnames in the request. Problem is, these hostnames end in .localhost which isn't being resolved by DNS, so the iPad doesn't know where myapp2.localhost is, and ...
localhost is device-specific, so visiting it on your iPad is is taking you to a page on your iPad itself (that probably doesn't exist).
To access a page that is served from your Mac from your iPad, use the Mac's local IP address instead of localhost. To get your Mac's local IP, open the Network pane of System Preferences. Select your active network on the ...
If you have a look at the main Apache2 config file, /etc/apache2/httpd.conf you will see that there are two things that have to be done to allow /Library/WebServer/CGI-Executables contain the cgi files.
First, since it isn't covered by the permissions for the document directory next to it, it will need a "Directory" block to define the permissions for all ...
You need to add a conf file to the following dir
Options Indexes MultiViews
Allow from All
For my own outward-facing servers, I did everything from within the built-in server software itself, except managing virtual hosts, for which task I used VirtualHostX.
The best tutorial I know for configuring Mavericks for web server use is done by Charles Edge, at his site, Krypted. I followed this same process essentially, and thus far, I've seen no ...
The difference is that 800 < 1024, but 8080 ≥ 1024.
Ports with numbers less than 1024 are privileged ports (google that) on Unix like systems, which means that only processes which run as root are allowed to listen to them.
If you don't want to recompile Bash yourself, the folks at TenFourFox (who make a PPC version of Firefox) have compiled a binary that works on OS X 10.4 - 10.9 on both PPC and Intel Macs, and have terminal instructions for installing:
At the time of writing (Sept 30) they've ...
sudo lsof -n -i :8080 -s TCP:LISTEN
The first two columns will be the name and PID of the process(es) listening on port 8080.
Use the PID to find it in Activity Monitor, Get Info, and notice which files it has open. It'll have a bunch of libraries open, but high on the list will be the executable file.
Alternatively, from the name, see what service ...
The answer you got was correct.
www.cnn.com canonical name = turner.map.fastly.net.
A canonical name, or CNAME record is a record in DNS servers that define an alias for another domain. In this case "www.cnn.com" points to the domain "turner.map.fastly.net".
As for your 192.168.1.1 server, that's most likely your router that is configured as a DNS cache ...