remmargorp
-
Posts
26 -
Joined
-
Last visited
Never
remmargorp's Achievements
Newbie (1/5)
0
Reputation
-
Wouldn't you want to change all $var's to $test1 in your example code? I have added test code for you to try out [code] <html> <body> <a href="document.php?test=10">Click Link</a><br><br> <?php $sSelf = $_SERVER['PHP_SELF']; echo $sSelf . "<br>\n"; $sTest = $_GET['test']; echo $sTest . "\n"; ?> </body> </html> [/code] Run the test code above, change document.php to whatever the document name is (so you can click the link to set test to equal 10). Should output this (when viewing source) when test = nothing: [code] <html> <body> <a href="document.php?test=10">Click Link</a><br><br> document.php<br> </body> </html> [/code] Should look like this (when you view source) when you click the link: [code] <html> <body> <a href="document.php?test=10">Click Link</a><br><br> document.php<br> 10 </body> </html> [/code] Give the source and content of the page when you load it, then when you click the link.
-
Make sure apache is working properly in the first place. Change the listening port to something like 50123, restart apache then connect to http://localhost:50123/ or http://127.0.0.1:50123/ If that fails, it is more than likely in the apache installation/configuration. If that does not fail, then it would be a port issue regarding port 80. With the apache service off run: netstat -n -a Copy the contents here so we can look at it
-
php exec() doesn't write to disc after apache restart
remmargorp replied to faraway's topic in Apache HTTP Server
I bet when apache starts during system boot it is started by/owned by a user with privileges. Where as when you re-start the service it probably does not retain the privileges it received at system boot. Which is a problem in two different ways. Either the intention is to have the Apache service owned/ran by a user with those type of privileges and you have the problem you are having. Or it is not your intention, and the Apache service has rights to stuff it shouldn't (security issue). Restart the machine, find out what user rights the apache service is running under, then restart the apache service and check again. -
[quote author=the_oliver link=topic=115709.msg471659#msg471659 date=1164150779] Works fine from hear! Schools are normaly very restrictive on trafic in/out for odvoius resions, primarily through port blocking. Why are you usingg :8080 / :80 would probably work. If its becouse your router uses this port its self, try another comon one your not using. For example if your running a windows only network your inlikly to use :22 (ssh and pcanyware normaly). Haveing to manditarly add a port just meens more for prople to remember when trying to get there! [/quote] A lot of ISP's block port 80. Using any port besides port 80 (or enabling SSL and using port 443) would require that you enter :port after the domain/IP, so using a common port works, but when you're giving it to someone that is not familiar with ports (the majority of online users) it doesn't really matter what port you give them. Port 23 to most people is just like port 4044, it's all the same to the typical end user (whereas we know port 23 to be commonly used for telnet)
-
I can access it. Could be blocked by your schools firewall or content filter (more likely firewall). Try changing the listening port to something less common.
-
Something else is already using that port. Could be an another instance of Apache, or another program or firewall software.
-
It's using the webmail domain because it becomes the "default domain". The default domain is the first one specified. Try changing it to: -------------------------------- NameVirtualHost *:81 <VirtualHost *> ServerName www.domain.net DocumentRoot /var/www/htdocs/ </VirtualHost> <VirtualHost *> ServerName webmail.domain.net DocumentRoot /var/www/htdocs/webmail </VirtualHost> -------------------------------- Putting the www.domain.net virtualhost first, this would make it the default domain. You could also add a virtualhost for servername domain.net, and it would use that, I would suggest changing the www.domain.net to be the default domain
-
I would assume not. Typically, if you own domain ####.com, then ####.com has a DNS record with some DNS server on the public internet. You would usually then have a DNS server on that domain, requests for ####.com or X.####.com would goto the domains DNS server and resolve accordingly. For example: your web browser tries to resolve http://xyz.abc.com, it checks its local DNS cache and returns nothing, so it goes to its DNS server, that DNS doesn't know anything so it goes to the ISP's DNS server, that DNS server doesn't know anything about xyz.abc.com but it does know about abc.com so it forwards it to abc.com's DNS server, abc.com's DNS server then resolve xyz.abc.com to an IP address that it has in its DNS records. Now, if your webserver has two IPs associated with it, and those IPs happen to be what is returned by resolving www.####.com and ####.com then it is an issue with Apache.
-
Does www.####.com resolve to the same IP address as ####.com? If not then you need to update your DNS records for www to point to the same IP that ####.com resovles to. If they are the same, it could be in the apache config (I would assume). Do a simple test and ping www.####.com and ####.com and see if they are the same.
-
It depends on what you serve. 1 megabit is 128 kilobytes "Essentially" you can serve 10 people the same 12.8 kilobyte page at the same time. In reality it can handle more than that
-
Maybe you can't actually pass 404 as a status... I'll have to check it out later
-
With hosting a server like that, your primary concern would be with upload bandwidth. Also, if your provider has any bandwidth limitations. For example, your upload may be 1Mbps, but they may only allow you 20GB total per month. 1 Mb upload should be fine for what you're looking to do.
-
RedirectMatch allows for status to be passed. The syntax for RedirectMatch is as follows (if I remember): RedirectMatch status regex URL Where status is optional and default is 302 RedirectMatch 404 ^/(director1|director2)/.*$ /point/to/errDoc.html I also just found this in the apache docs for mod_rewrite: Although rewrite rules are syntactically permitted in <Location> sections, this should never be necessary and is unsupported.
-
It depends on how much data you plan on transferring/what you're serving.
-
Try <LocationMatch "/(director1|director3)/"> RewriteRule ^.*$ http://www.site.com/ErrorDocument ErrorDocument 404 /ErrorDocument.html </LocationMatch>