<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sat, 18 May 2013 15:48:25 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Chris Shiflett's Blog: SERVER_NAME Versus HTTP_HOST]]></title>
      <guid>http://www.phpdeveloper.org/news/5003</guid>
      <link>http://www.phpdeveloper.org/news/5003</link>
      <description><![CDATA[On <i>Chris Shiflett</i>'s blog, there's <a href="http://shiflett.org/archive/211">a post</a> that looks a an issue that's been brought up on the <a href="http://www.nyphp.org/">New York PHP</a> mailing list concerning two variables in the $_SERVER superglobal - SERVER_NAME and HTTP_POST.
<p>
The question initially was "arean't these the same thing?" Chris answers:
<p>
<quote>
<i>
There were several informative replies within the first few minutes, but there's more to this question than most people realize. In fact, I'm reminded of a blog entry from Zeev last year, where he warns against $_SERVER['SERVER_NAME'].
</i>
</quote>
<p>
Zeev suggests that SERVER_NAME is pulled from the Host header from the remote user. Chris <a href="http://shiflett.org/archive/211">reminds us</a>, also, of some disagreements with this view Zeev presented, namely from Rasmus. Chris then gives an example script to illustrate hos things area really handled - the variables use the given values when they're present in the request, but they still do default back to the ServerName when absent (so only in certain circumstances).]]></description>
      <pubDate>Fri, 17 Mar 2006 06:53:14 -0600</pubDate>
    </item>
  </channel>
</rss>
