* bug#19729: 25.0.50; url-retrieve-synchronously never returns when there's no response from the server
@ 2015-01-29 21:11 Dmitry Gutov
2015-01-29 22:23 ` Andreas Schwab
0 siblings, 1 reply; 9+ messages in thread
From: Dmitry Gutov @ 2015-01-29 21:11 UTC (permalink / raw)
To: 19729
Evaluate
(url-retrieve-synchronously "http://localhost:3333/foo")
As long as there's nothing running on that port, the function call
should return quickly, but it never completes.
On emacs-24, it works as expected.
In GNU Emacs 25.0.50.9 (x86_64-unknown-linux-gnu, GTK+ Version 3.12.2)
of 2015-01-29 on axl
Repository revision: 1dc1959ebf50401c69adeb6d182950b59835f94d
Windowing system distributor `The X.Org Foundation', version 11.0.11601901
System Description: Ubuntu 14.10
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#19729: 25.0.50; url-retrieve-synchronously never returns when there's no response from the server
2015-01-29 21:11 bug#19729: 25.0.50; url-retrieve-synchronously never returns when there's no response from the server Dmitry Gutov
@ 2015-01-29 22:23 ` Andreas Schwab
2015-01-29 22:24 ` Dmitry Gutov
2015-01-29 22:25 ` Dmitry Gutov
0 siblings, 2 replies; 9+ messages in thread
From: Andreas Schwab @ 2015-01-29 22:23 UTC (permalink / raw)
To: Dmitry Gutov; +Cc: 19729
Dmitry Gutov <dgutov@yandex.ru> writes:
> Evaluate
>
> (url-retrieve-synchronously "http://localhost:3333/foo")
>
> As long as there's nothing running on that port, the function call
> should return quickly, but it never completes.
If nothing answers then it will wait until TCP timeout.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#19729: 25.0.50; url-retrieve-synchronously never returns when there's no response from the server
2015-01-29 22:23 ` Andreas Schwab
@ 2015-01-29 22:24 ` Dmitry Gutov
2015-01-30 10:39 ` Andreas Schwab
2015-01-29 22:25 ` Dmitry Gutov
1 sibling, 1 reply; 9+ messages in thread
From: Dmitry Gutov @ 2015-01-29 22:24 UTC (permalink / raw)
To: Andreas Schwab; +Cc: 19729
On 01/30/2015 12:23 AM, Andreas Schwab wrote:
> If nothing answers then it will wait until TCP timeout.
Does "never completes" sound like honouring TCP timeout to you?
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#19729: 25.0.50; url-retrieve-synchronously never returns when there's no response from the server
2015-01-29 22:24 ` Dmitry Gutov
@ 2015-01-30 10:39 ` Andreas Schwab
2015-01-30 10:43 ` Dmitry Gutov
0 siblings, 1 reply; 9+ messages in thread
From: Andreas Schwab @ 2015-01-30 10:39 UTC (permalink / raw)
To: Dmitry Gutov; +Cc: 19729
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 01/30/2015 12:23 AM, Andreas Schwab wrote:
>> If nothing answers then it will wait until TCP timeout.
>
> Does "never completes" sound like honouring TCP timeout to you?
You didn't say how long "never" is.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#19729: 25.0.50; url-retrieve-synchronously never returns when there's no response from the server
2015-01-29 22:23 ` Andreas Schwab
2015-01-29 22:24 ` Dmitry Gutov
@ 2015-01-29 22:25 ` Dmitry Gutov
2015-01-30 10:22 ` Andreas Schwab
1 sibling, 1 reply; 9+ messages in thread
From: Dmitry Gutov @ 2015-01-29 22:25 UTC (permalink / raw)
To: Andreas Schwab; +Cc: 19729
On 01/30/2015 12:23 AM, Andreas Schwab wrote:
> If nothing answers then it will wait until TCP timeout.
But actually, the port is closed, so it should finish immediately with
"connection refused".
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#19729: 25.0.50; url-retrieve-synchronously never returns when there's no response from the server
2015-01-29 22:25 ` Dmitry Gutov
@ 2015-01-30 10:22 ` Andreas Schwab
2015-01-30 10:41 ` Dmitry Gutov
0 siblings, 1 reply; 9+ messages in thread
From: Andreas Schwab @ 2015-01-30 10:22 UTC (permalink / raw)
To: Dmitry Gutov; +Cc: 19729
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 01/30/2015 12:23 AM, Andreas Schwab wrote:
>
>> If nothing answers then it will wait until TCP timeout.
>
> But actually, the port is closed, so it should finish immediately with
> "connection refused".
Depends on the firewall settings.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#19729: 25.0.50; url-retrieve-synchronously never returns when there's no response from the server
2015-01-30 10:22 ` Andreas Schwab
@ 2015-01-30 10:41 ` Dmitry Gutov
0 siblings, 0 replies; 9+ messages in thread
From: Dmitry Gutov @ 2015-01-30 10:41 UTC (permalink / raw)
To: Andreas Schwab; +Cc: 19729
On 01/30/2015 12:22 PM, Andreas Schwab wrote:
> Depends on the firewall settings.
Nothing above the default Ubuntu settings. Like I said, emacs-24 works
like expected.
Have you tried my example? Can you see the difference in behavior?
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2015-01-30 14:15 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-01-29 21:11 bug#19729: 25.0.50; url-retrieve-synchronously never returns when there's no response from the server Dmitry Gutov
2015-01-29 22:23 ` Andreas Schwab
2015-01-29 22:24 ` Dmitry Gutov
2015-01-30 10:39 ` Andreas Schwab
2015-01-30 10:43 ` Dmitry Gutov
2015-01-30 14:15 ` Andreas Schwab
2015-01-29 22:25 ` Dmitry Gutov
2015-01-30 10:22 ` Andreas Schwab
2015-01-30 10:41 ` Dmitry Gutov
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).