On 01.08.2012 01:57, icorderi wrote:
@Rob Yes localhost is translated to 127.0.0.1 on hosts. But
regardless of that, if the wcf service is hosted as
net.tcp://localhost:8081 it should work as expected.
I would expect it to use localhost if localhost is specified.
An easy workaround is to
1) My original fix for 2663 i knew would be slower than the original
without it because it had to do more to handle all possibilties for ors
introduced with bug 2663's report. For those unfamiliar -- (A|AB|ABC)
if you tried to match that against ABC it would first match with A
(which is valid)
On 7/31/2012 5:45 PM, icorderi wrote:
Basically, when you host the wcf service on the console with a uri like
net.tcp://localhost:8081 on a linux box the socket address is not bind to
listen on 0.0.0.0:8081 instead it listens on 127.0.0.1:8081 essentially
refusing all connections from other
Although you ask, you probably already know the answer: correctness is
preferable to speed. Sure, if we can have both, that'd be great, but if we
had to choose, let's be correct.
Rob Wilkens wrote
1) My original fix for 2663 i knew would be slower than the original
without it because it had
David Schmitt wrote
Isn't there a wildcard syntax or something like that? Hmm: Fourth hit on
Google:
http://stackoverflow.com/q/10649078/4918
The point is to replace host name in base address with * symbol
(wildcard). It will be changed with actual host name in run time.
Tested
On 08/01/2012 02:44 PM, icorderi wrote:
David Schmitt wrote
Isn't there a wildcard syntax or something like that? Hmm: Fourth hit on
Google:
http://stackoverflow.com/q/10649078/4918
The point is to replace host name in base address with * symbol
(wildcard). It will be changed with
