emacs-diffs
[Top][All Lists]
Advanced

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

[Emacs-diffs] Changes to emacs/admin/FOR-RELEASE


From: Richard M . Stallman
Subject: [Emacs-diffs] Changes to emacs/admin/FOR-RELEASE
Date: Mon, 03 Jan 2005 16:12:31 -0500

Index: emacs/admin/FOR-RELEASE
diff -c emacs/admin/FOR-RELEASE:1.36 emacs/admin/FOR-RELEASE:1.37
*** emacs/admin/FOR-RELEASE:1.36        Mon Jan  3 03:20:06 2005
--- emacs/admin/FOR-RELEASE     Mon Jan  3 21:00:07 2005
***************
*** 32,37 ****
--- 32,40 ----
  
  ** Fix up url-ldap.el.
  
+ ** url/*.el has lots of `(declare (special ...))' which
+ are meaningless.  What's that trying to do?
+ 
  * BUGS
  
  ** Incomplete overlay mouse-face highlight bug (Ralf Angeli, Oct 18)
***************
*** 62,103 ****
  I think in the near future we will see more of this problem, so it might be
  time to make anfe-ftp more intelligent.
  
- ** Bug in url-http-parse-headers, reported in
- From: Vivek Dasmohapatra <address@hidden>
- Date: Tue, 28 Sep 2004 16:13:13 +0100
- 
- Fetching a url with url-retrieve can reult in an anrbitrary buffer
- being killed if a 401 (or possibly a 407) result is encountered:
- 
- url-http-parse-headers calls url-http-handle-authentication,
- which can call url-retrieve.
- 
- This results in the current buffer being killed, and a new http buffer
- being generated. However, when the old http buffer is killed, emacs
- picks the top buffer from the list as the new current buffer, so by the
- time we get to the end of url-http-parse-headers, _that_ buffer is marked
- as dead even though it is not necessarily a url buffer, so next time the
- url libraries reap their dead buffers, an innocent bystander buffer is
- killed instead (and an obsolete http buffer may be left lying around too).
- 
- A possible fix (which I am currently using) is to call set-buffer
- on the return value of url-http-parse-headers:
- 
-       (case url-http-response-status
-       (401
-        ;; The request requires user authentication.  The response
-        ;; MUST include a WWW-Authenticate header field containing a
-        ;; challenge applicable to the requested resource.  The
-        ;; client MAY repeat the request with a suitable
-        ;; Authorization header field.
-        (url-mark-buffer-as-dead (current-buffer))
-        (set-buffer (url-http-handle-authentication nil)))
- etc ....
- 
- which makes sure that it is the right http buffer that is current when
- we come to mark the http buffers as dead.
- 
- 
  
  * GTK RELATED BUGS
  
--- 65,70 ----




reply via email to

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