Problems with URL Syntax

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Jerry Spence1

    Problems with URL Syntax

    I am trying to get a jpg image as follows:

    Dim Client As System.Net.WebC lient = New System.Net.WebC lient
    Client.Download File("http://root:<password> @192.168.0.99/cgi-bin/video.jpg",
    MyFilename)

    However I understand that IE no longer supports this 'in-line' presentation
    of the username and password strings. Indeed I am getting a "Not Authorized"
    error being returned.

    Although I'm not using IE directly, are the components (and the security
    contraints) of IE still being used in the background?

    Has anyone met this before and is there a work around?

    Thanks

    -Jerry


  • Herfried K. Wagner [MVP]

    #2
    Re: Problems with URL Syntax

    "Jerry Spence1" <jerry.spence@s omewhere.com> schrieb:[color=blue]
    >I am trying to get a jpg image as follows:
    >
    > Dim Client As System.Net.WebC lient = New System.Net.WebC lient
    > Client.Download File("http://root:<password> @192.168.0.99/cgi-bin/video.jpg",
    > MyFilename)
    >
    > However I understand that IE no longer supports this 'in-line'
    > presentation of the username and password strings. Indeed I am getting a
    > "Not Authorized" error being returned.[/color]

    It's nowhere specified that username and password can be embedded inside
    HTTP URIs (this does not apply to FTP URIs though), and only some browsers
    supported this sort of URIs. However, embedding username and password into
    URIs is a very bad idea for security reasons. Instead you may want to check
    out the 'WebClient' object's 'Credentials' property which can be used to
    pass authentication data to the server.
    [color=blue]
    > Although I'm not using IE directly, are the components (and the security
    > contraints) of IE still being used in the background?[/color]

    No, 'WebClient' has nothing to do with IE. It was simply IE which provided
    functionality which was not standard compliant and insecure and has been
    abandoned for this reason.

    --
    M S Herfried K. Wagner
    M V P <URL:http://dotnet.mvps.org/>
    V B <URL:http://classicvb.org/petition/>

    Comment

    • Jerry Spence1

      #3
      Re: Problems with URL Syntax


      "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message
      news:%239zoCRAg GHA.1260@TK2MSF TNGP05.phx.gbl. ..[color=blue]
      > "Jerry Spence1" <jerry.spence@s omewhere.com> schrieb:[color=green]
      >>I am trying to get a jpg image as follows:
      >>
      >> Dim Client As System.Net.WebC lient = New System.Net.WebC lient
      >> Client.Download File("http://root:<password> @192.168.0.99/cgi-bin/video.jpg",
      >> MyFilename)
      >>
      >> However I understand that IE no longer supports this 'in-line'
      >> presentation of the username and password strings. Indeed I am getting a
      >> "Not Authorized" error being returned.[/color]
      >
      > It's nowhere specified that username and password can be embedded inside
      > HTTP URIs (this does not apply to FTP URIs though), and only some browsers
      > supported this sort of URIs. However, embedding username and password
      > into URIs is a very bad idea for security reasons. Instead you may want
      > to check out the 'WebClient' object's 'Credentials' property which can be
      > used to pass authentication data to the server.
      >[color=green]
      >> Although I'm not using IE directly, are the components (and the security
      >> contraints) of IE still being used in the background?[/color]
      >
      > No, 'WebClient' has nothing to do with IE. It was simply IE which
      > provided functionality which was not standard compliant and insecure and
      > has been abandoned for this reason.
      >
      > --
      > M S Herfried K. Wagner
      > M V P <URL:http://dotnet.mvps.org/>
      > V B <URL:http://classicvb.org/petition/>[/color]

      Credentials worked a treat. Thank you so much!

      -Jerry


      Comment

      Working...