Re: losing the :80 off URLs

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Graham Barr: "Re: Status Check: libwww on !unix platforms"
• Previous message: Tom Christiansen: "Status Check: libwww on !unix platforms"
• Maybe in reply to: Neil Bowers: "losing the :80 off URLs"

Do programmers usually discuss grammar?

As per dropping the port, I found that on solaris with libwww-perl, if you
send a URL to a get request w/o parsing it through URI::URL and it has port
information, especially (:8001), it is much more likely to throw a Broken
Pipe error message.

If you do expirement with retaining the ports, perhaps it should be a
seperate call.

-Craig Wood

>>Our problem arises because we have various Berkeley DB files keyed on URL's,
>>so it's important that the :80 is retained if it was there in the first place.
>
>Um, I think you mean it's important that it *be* retained, don't you?
>These are very different:
>
>    It's important that she be here.  [she isn't here, but ought to be]
>
>    It's important that she is here.  [she is here, which means something]
>
>I always scratch my head when I read the opposite usage, because
>it makes me wonder what subtlety I'm missing.  In this case, 
>I *think* it's nothing, but one still wonders.
>
>--tom
>
>

• Next message: Graham Barr: "Re: Status Check: libwww on !unix platforms"
• Previous message: Tom Christiansen: "Status Check: libwww on !unix platforms"
• Maybe in reply to: Neil Bowers: "losing the :80 off URLs"