Bug 12153 - Slim::Networking::Async fails to follow redirects
: Slim::Networking::Async fails to follow redirects
Status: RESOLVED DUPLICATE of bug 12276
Product: Logitech Media Server
Classification: Unclassified
Component: Misc
: 7.4.0
: PC Other
: -- normal (vote)
: 7.4.0
Assigned To: Andy Grundman
: SQLite
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-25 03:43 UTC by Michael Herger
Modified: 2009-06-05 01:19 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Herger 2009-05-25 03:43:09 UTC
TinySC (only) fails to check for updates on updates.squeezenetwork.com due to some failure following the redirect to www.sn.com. Using the latter instead is working fine. 

[09-05-25 12:27:33.1566] Slim::Utils::Misc::msg (1154) Warning: [12:27:33.1564] Use of uninitialized value in subroutine entry at /Users/mh/Documents/workspace/noweb-sqlite/server/Slim/Networking/IO/Select.pm line 116.
[09-05-25 12:27:33.1570] Slim::Networking::IO::Select::__ANON__ (113) Error: Select task failed calling Slim::Networking::Async::_async_read: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /Users/mh/Documents/workspace/noweb-sqlite/server/Slim/Networking/IO/Select.pm line 116.

Obviously it doesn't like the socket. If I do not disconnect it before the redirection, everything seems to be fine, except that I'm not sure this is save :-)

Index: server/Slim/Networking/Async/HTTP.pm
===================================================================
--- server/Slim/Networking/Async/HTTP.pm	(revision 26724)
+++ server/Slim/Networking/Async/HTTP.pm	(working copy)
@@ -336,7 +336,7 @@
 			# check max redirects
 			if ( $location && scalar @{$previous} < $self->maxRedirect ) {
 				
-				$self->disconnect;
+#				$self->disconnect;
 			
 				# change the request object to the new location
 				delete $args->{request};
Comment 1 Michael Herger 2009-06-05 01:19:48 UTC

*** This bug has been marked as a duplicate of bug 12276 ***