none
Duplicated proxy exceptions cause strange issue RRS feed

  • Question

  • Hi Guys,

    We have some thin client applications, which run within our local intranet zone (send http queries to a local server - ex. "ourserver01.ourprefix.oursuffix") and should have no communicate with our proxy.

    If the proxy exceptions list contains only "*.ourprefix.oursuffix" everything work as expected, but if I append an other exception ended with the same ".ourprefix.oursuffix" for example "*.ourprefix.oursuffix;ourserver02.ourprefix.oursuffix" the client starts to send packages to our proxy, which causes issues.

    I know if I use wildcard (*) other exceptions are unnecessary to use, but I would like to know the reason of this behaviour.

    Thanks

    Jim

    Thursday, November 13, 2014 7:10 PM

Answers

All replies

  • If the proxy exceptions list contains only "*.ourprefix.oursuffix" everything work as expected, but if I append an other exception ended with the same ".ourprefix.oursuffix" for example "*.ourprefix.oursuffix;ourserver02.ourprefix.oursuffix" the client starts to send packages to our proxy, which causes issues.

    Hi Jim,

    May I know the reason why you use these duplicated proxy exceptions:  "*.ourprefix.oursuffix;ourserver02.ourprefix.oursuffix"?

    As I know, add a wildcard at the beginning of an Internet address, IP address, or domain name will bypass servers with a common ending. For example, use "*.example.com" will bypass any entries ending in ".example.com" (such as "some.example.com" and "www.example.com"). Just as you mentioned in the last sentence, it's not necessary to use other exceptions if you use a * at the beginning.


    Yolanda Zhu
    TechNet Community Support

    Monday, November 17, 2014 2:53 AM
    Moderator
  • Hi,

    Thanks for your answer.

    It was a mistake in a long exception list, and I have never thought that it would cause any issue if I add an additional exception with a wildcard * to the list, where an exception is already exists with the same ending.

    We use more proxies and I had to check all the exception lists because of that behaviour, thats why I wanted to know the reason of this. That would better if the proxy would simply ignore the first exception, when found one in the following list with wildcard with the same ending.

    Jim

    Tuesday, November 18, 2014 1:07 PM
  • Hi,

    According to my knownledge, it should just bypass the proxy exception: ourserver02.ourprefix.oursuffix, but seems things different in your situation, simple workground at this moment is removing the un-needed exceptions, but if this is not possible, then I suggest you use a network monitor tool to view the detailed network trace in your environment and see what happened.

    http://technet.microsoft.com/en-us/library/cc939852.aspx

    http://technet.microsoft.com/en-us/library/dd361953.aspx


    Yolanda Zhu
    TechNet Community Support

    Monday, November 24, 2014 3:09 AM
    Moderator