Netsh Commands for Windows Hypertext Transfer Protocol (WINHTTP)
Applies To: Windows Server 2008
You can use commands in the netsh winhttp context to configure proxy and tracing settings for Windows HTTP. The Netsh commands for winhttp can be run manually at the netsh prompt or in scripts and batch files.
To run these commands from the command prompt, you must either enter the netsh winhttp context or prepend the context to the command. For example, if you are at the command prompt but have not typed netsh and then winhttp to enter the netsh winhttp context, you must type:
netsh winhttp command
Where command is the command that you want to run, including all of the required parameters for the command.
For information on how to interpret netsh command syntax, see Formatting Legend.
This section contains the following commands:
Netsh winhttp commands
The following entries provide details for each command.
Flushes the internal buffers for the log files.
Imports the proxy settings in the Internet Explorer Web browser's Internet Options. Importing settings from IE is the only available option
import proxy source =ie
Resets the WinHTTP proxy setting to DIRECT.
Resets the WinHTTP trace parameters to the default settings.
Following are the default WinHTTP trace parameters:
Configures the WinHTTP proxy setting.
set proxy [proxy-server=] ProxyServerName [bypass-list=] <HostsList>
Following are three examples of how to use the set proxy command.
set proxy myproxy set proxy myproxy:80 "<local>bar" set proxy proxy-server="http=myproxy;https=sproxy:88" bypass-list="*.contoso.com"
Configures the WinHTTP tracing parameters.
set tracing [output=] file | debugger | both [trace-file-prefix=] FilePrefix [level=] default | verbose [format=] ansi | hex [max-trace-file-size=] FileSize [state=] enabled |disabled
Following are two examples of how to use the set tracing command.
set tracing trace-file-prefix="C:\Temp\Test3" level=verbose format=hex set tracing output=debugger max-trace-file-size=512000 state=enabled
Displays the current WinHTTP proxy setting.
Displays the current WinHTTP tracing parameters.
Agreed, explaining <local>bar is not a technical question it's a question about the content (or lack of content) of the document. <local> refers to all short name hosts. What is <local>bar ? Should it read <local>;bar perhaps?? Still begs the question what bar means in this context. bar alone would be a short named host so already covered by <local> so why is it there. bar.com maybe would make more sense.
Is this just a typo in the documentation and poor response from a support person who doesn't have a clue and can't be bothered to try and understand.
If the examples aren't explained and don't appear to be valid, then the fault is with the document not the technical understanding of the reader. We come here to be educated not to be more confused.
That's not cool
The question posted directly pertains to clarifying the documentation as laid out. There's no problem they're trying to get you to solve for them, just making specific query regarding this specific document. Moving it to Technet would be ridiculous.