HTTP Status codes via Powershell

Question

Somehow the below codes works fine for the first few test URLs within C:\testurl.txt then it hung up forever when it is processing the 4th URL from the C:\testurl.txt , no idea why it hangs up?

It is already working fine for up to 3 URLs but stuck up on 4th onward

CLS
$urllist = Get-Content "C:\testurl.txt" # URLs to test one in each line
foreach ($url in $urllist) {
    Write-Host $url

    $req = [System.Net.WebRequest]::Create($url)

    try {
        $res = $req.GetResponse()
    } catch [System.Net.WebException] {
        $res = $_.Exception.Response
    }

    $res.StatusCode
    #Print OK or whatever

    [int]$res.StatusCode
    #Print 200 or whatever
}

It is working fine for up to 3 URLs but hangs the script on 4th URL without any output or error message. Here is the example of c:\testurl.txt

http://www.google.com
http://www.google.com     
http://www.google.com
http://www.google.com
http://www.hotmail.com
http://www.gmail.com
http://www.yahoo.com
http://www.msn.com

Please note each URL will be in a new line, you will see that script will stop at (the 4th one) you may try with your own URLs, etc too

Ansgar Wiechers If you add multiple URLs to test in the file c:\testurl.txt for example: www.google.com www.hotmail.com www.gmail.com www.yahoo.com www.msn.com then you you will see that script will stop at www.yahoo.com (the 4th one) — M-A Charlotte
– M-A Charlotte, Commented Aug 6, 2019 at 15:23
No, it doesn't. It will throw an error for all of them if you specify just the FQDNs without protocol scheme, though. — Ansgar Wiechers
– Ansgar Wiechers, Commented Aug 6, 2019 at 15:31
@M-ACharlotte - PLEASE add the list to your ORIGINAL POST. [frown] — Lee_Dailey
– Lee_Dailey, Commented Aug 6, 2019 at 15:46
@M-ACharlotte - good! now ... put them in code format so that folks can read them ... [grin] — Lee_Dailey
– Lee_Dailey, Commented Aug 6, 2019 at 15:54

Mathias R. Jessen · Accepted Answer · 2024-07-29 09:57:02Z

5

then it hung up forever

No - it's hung until the underlying TCP connections of the previous requests time out.

The .NET CLR will internally pool all WebRequest dispatches so that only a finite number of external requests will be initiated concurrently, and as long as you have a number of un-closed WebResponse objects in memory, your requests will start queuing up.

You can avoid this by closing them (as you should):

foreach ($url in $urllist) {
    Write-Host $url

    $req = [System.Net.WebRequest]::Create($url)

    try {
        $res = $req.GetResponse()
    } 
    catch [System.Net.WebException] {
        $res = $_.Exception.Response
    }
    finally {
        if ($res -is [System.Net.WebResponse]) {
            $res.StatusCode
            #Print OK or whatever

            [int]$res.StatusCode
            #Print 200 or whatever

            $res.Dispose()
            # close connection, dispose of response stream
        }
    }
}

edited Jul 29, 2024 at 9:57

answered Aug 6, 2019 at 16:17

Mathias R. Jessen

178k13 gold badges175 silver badges234 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

M-A Charlotte Over a year ago

Its perfect! I missed out that Disposing of the stream and that's why it was hanging up after a few URLs, Thanks for the help!

Collectives™ on Stack Overflow

HTTP Status codes via Powershell

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related