[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#11981: 24.1.50; url-http-parse-headers should not disable file name

From: David Engster
Subject: bug#11981: 24.1.50; url-http-parse-headers should not disable file name handlers since it breaks auth-source
Date: Wed, 18 Jul 2012 20:38:48 +0200

The function `url-http-parse-headers' temporarily disables all file name
handlers to circumvent a bug where Tramp could kick in because the URL
might look like a remote file (#6717). This is the offending snippet:

        ;; The filename part of a URL could be in remote file syntax,
        ;; see Bug#6717 for an example.  We disable file name
        ;; handlers, therefore.
        (file-name-handler-alist nil))

However, this workaraound assumes that everything that gets afterwards
in the `let'-section does not depend on file name handlers. However,
this is not the case: `url-http-handle-authentication' is called which
in turn calls the auth-source package. This package however supports
encrypted authinfo files which have to be automatically decrypted
through `auto-encryption-mode'. This, of course, works through file name

Here's a backtrace from `auth-source-search' resulting from a call to
`url-retrieve-synchronously' on a password-protected URL:

  auth-source-search(:max 1 :host "www.google.com:443" :port "https")
  url-do-auth-source-search("www.google.com:443" "https" :user)
  url-basic-auth([cl-struct-url "https" nil nil "www.google.com" 443  
"/calendar/dav/MY-GOOGLE-ACCOUNT/events/" nil nil t nil t] t nil "Google 
CalDAV" (("realm" . "Google CalDAV") ("basic")))
 "Google CalDAV" "basic" t (("realm" . "Google CalDAV") ("basic")))
  [ ... ]
  url-http-chunked-encoding-after-change-function(500 507 7)
  url-http-generic-filter(#<process www.google.com<1>> "\n0\n\n")
  [ ... ]

Note that after `url-http-parse-headers' the variable
`file-name-handler-alist' is set to 'nil', thus when
`auth-source-search' loads an encrypted authinfo.gpg file, it won't
automatically get decrypted.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]