Extract filename and path from URL in bash script

后端 未结 13 964
别跟我提以往
别跟我提以往 2021-01-30 14:17

In my bash script I need to extract just the path from the given URL. For example, from the variable containing string:

http://login:password@example.com/one/more/dir/fi

相关标签:
13条回答
  • 2021-01-30 14:20

    How does this :?

    echo 'http://login:password@example.com/one/more/dir/file.exe?a=sth&b=sth' | \
    sed 's|.*://[^/]*/\([^?]*\)?.*|/\1|g'
    
    • .://[^/]/: http://login:password@example.com/
    • ([^?]*) : one/more/dir/file.exe
    • ?.* : ?a=sth&b=sth
    • /\1 : /one/more/dir/file.exe
    0 讨论(0)
  • 2021-01-30 14:24

    If you have a gawk:

    $ echo 'http://login:password@example.com/one/more/dir/file.exe?a=sth&b=sth' | \
      gawk '$0=gensub(/http:\/\/[^/]+(\/[^?]+)\?.*/,"\\1",1)'
    

    or

    $ echo 'http://login:password@example.com/one/more/dir/file.exe?a=sth&b=sth' | \
      gawk -F'(http://[^/]+|?)' '$0=$2'
    

    Gnu awk can use regular expression as field separators(FS).

    0 讨论(0)
  • 2021-01-30 14:26

    Using only bash builtins:

    path="/${url#*://*/}" && [[ "/${url}" == "${path}" ]] && path="/"
    

    What this does is:

    1. remove the prefix *://*/ (so this would be your protocol and hostname+port)
    2. check if we actually succeeded in removing anything - if not, then this implies there was no third slash (assuming this is a well-formed URL)
    3. if there was no third slash, then the path is just /

    note: the quotation marks aren't actually needed here, but I find it easier to read with them in

    0 讨论(0)
  • 2021-01-30 14:28

    Best bet is to find a language that has a URL parsing library:

    url="http://login:password@example.com/one/more/dir/file.exe?a=sth&b=sth"
    path=$( echo "$url" | ruby -ruri -e 'puts URI.parse(gets.chomp).path' )
    

    or

    path=$( echo "$url" | perl -MURI -le 'chomp($url = <>); print URI->new($url)->path' )
    
    0 讨论(0)
  • 2021-01-30 14:30

    This uses bash and cut as another way of doing this. It's ugly, but it works (at least for the example). Sometimes I like to use what I call cut sieves to whittle down the information that I am actually looking for.

    Note: Performance wise, this may be a problem.

    Given those caveats:

    First let's echo the the line:

    echo 'http://login:password@example.com/one/more/dir/file.exe?a=sth&b=sth'
    

    Which gives us:

    http://login:password@example.com/one/more/dir/file.exe?a=sth&b=sth

    Then let's cut the line at the @ as a convenient way to strip out the http://login:password:

    echo 'http://login:password@example.com/one/more/dir/file.exe?a=sth&b=sth' | \
    cut -d@ -f2
    

    That give us this:

    example.com/one/more/dir/file.exe?a=sth&b=sth

    To get rid of the hostname, let's do another cut and use the / as the delimiter while asking cut to give us the second field and everything after (essentially, to the end of the line). It looks like this:

    echo 'http://login:password@example.com/one/more/dir/file.exe?a=sth&b=sth' | \
    cut -d@ -f2 | \
    cut -d/ -f2-
    

    Which, in turn, results in:

    one/more/dir/file.exe?a=sth&b=sth

    And finally, we want to strip off all the parameters from the end. Again, we'll use cut and this time the ? as the delimiter and tell it to give us just the first field. That brings us to the end and looks like this:

    echo 'http://login:password@example.com/one/more/dir/file.exe?a=sth&b=sth' | \
    cut -d@ -f2 | \
    cut -d/ -f2- | \
    cut -d? -f1
    

    And the output is:

    one/more/dir/file.exe

    Just another way to do it and this approach is one way to whittle away that data you don't need in an interactive way to come up with something you do need.

    If I wanted to stuff this into a variable in a script, I'd do something like this:

    #!/bin/bash
    
    url="http://login:password@example.com/one/more/dir/file.exe?a=sth&b=sth"
    file_path=$(echo ${url} | cut -d@ -f2 | cut -d/ -f2- | cut -d? -f1)
    echo ${file_path}
    

    Hope it helps.

    0 讨论(0)
  • 2021-01-30 14:33

    The Perl snippet is intriguing, and since Perl is present in most Linux distros, quite useful, but...It doesn't do the job completely. Specifically, there is a problem in translating the URL/URI format from UTF-8 into path Unicode. Let me give an example of the problem. The original URI may be:

    file:///home/username/Music/Jean-Michel%20Jarre/M%C3%A9tamorphoses/01%20-%20Je%20me%20souviens.mp3
    

    The corresponding path would be:

    /home/username/Music/Jean-Michel Jarre/Métamorphoses/01 - Je me souviens.mp3
    

    %20 became space, %C3%A9 became 'é'. Is there a Linux command, bash feature, or Perl script that can handle this transformation, or do I have to write a humongous series of sed substring substitutions? What about the reverse transformation, from path to URL/URI?

    (Follow-up)

    Looking at http://search.cpan.org/~gaas/URI-1.54/URI.pm, I first saw the as_iri method, but that was apparently missing from my Linux (or is not applicable, somehow). Turns out the solution is to replace the "->path" part with "->file". You can then break that further down using basename and dirname, etc. The solution is thus:

    path=$( echo "$url" | perl -MURI -le 'chomp($url = <>); print URI->new($url)->file' )
    

    Oddly, using "->dir" instead of "->file" does NOT extract the directory part: rather, it formats the URI so it can be used as an argument to mkdir and the like.

    (Further follow-up)

    Any reason why the line cannot be shortened to this?

    path=$( echo "$url" | perl -MURI -le 'print URI->new(<>)->file' )
    
    0 讨论(0)
提交回复
热议问题