Re^3: Found a Perl hole

Replies are listed 'Best First'.
Re^4: Found a Perl hole by gellyfish (Monsignor) on Jan 28, 2005 at 10:30 UTC
There's no difference between a domain name and an ip, Even if that were actually true in the general case ( I won't bother going into a discussion of DNS CNAMEs, Round Robin DNS and named virtual hosts here) - the HTTP/1.1 specification (RFC2616) states quite unequivocally: The use of IP addresses in URLs SHOULD be avoided whenever possible.. /J\	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.
Re^4: Found a Perl hole by shenme (Priest) on Jan 28, 2005 at 05:07 UTC
Somebody explained on CB that their company's web proxy would not allow URL's with IP addresses. (They did try to look at your code) I'd not heard of that before, but then, that's why you shouldn't pre-judge why someone says another way is 'better'.	[reply]
Re^5: Found a Perl hole by kutsu (Priest) on Jan 28, 2005 at 14:25 UTC
That was me, and hence I can't help NewToYou! with his code. Though I could bypass my proxy...I'm not going to risk my job over this bit o'code. However, the fact that your site may (and proably will) change long before this thread changes is a better reason to post the actual code. "Cogito cogito ergo cogito sum - I think that I think, therefore I think that I am." Ambrose Bierce	[reply]
Re^4: Found a Perl hole by PhilHibbs (Hermit) on Jan 28, 2005 at 11:54 UTC
Clicking on a link is not impossible, but pointless when the server returns "File not found". These discussions are frequently referred back to by people searching PM, and having gaping holes in the conversation history is unhelpful.	[reply]