Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Media server URLs invalid for IPv6 enabled hosts
#1
On an IPv6 enabled system, right click on a torrent, content, media server, "copy local stream URI to clipboard" generates an invalid URL when IPv6 is enabled and has an IP on the system.  For example, it gives me:

http://fe80:0:0:a:38a4:ab5c:1610:8b33%3:57492/Content/4AF364207FBF4F5272E5CFD325AF48CD1B134CF2-0.mkv

First, an IPv6 IP used in a URI should be enclosed in brackets (since : is used in the IP and to indicate port).  Second, I'm not sure what the "%3" is but that doesn't seem right.  A URI more like what I'd expect would be:

http://[fe80:0:0:a:38a4:ab5c:1610:8b33]:57492/Content/4AF364207FBF4F5272E5CFD325AF48CD1B134CF2-0.mkv

The URI Vuze provides does not work in VLC.  If I modify the URI as shown and give that to VLC, it works and I get video.

System:

Java 1.8.0_51
 Oracle Corporation
SWT v4508, win32
Windows 8.1 v6.3, amd64
V5.6.2.0/4 az3

Pretty standard dual-stack IPv4+IPv6 network config.  I didn't do anything to make Vuze choose IPv6 for this, it selected that IP automatically when I asked for a local URI.  Oh, and I'm on Win10 pro even though that says 8.1 in Vuze's system info output.  If you need anything more, just ask, though I suspect this is easy to replicate on any IPv6 enabled system.
Reply
#2
Regarding '%' check out

https://en.wikipedia.org/wiki/IPv6_addre...ne_indices

Looks like it should be URL encoded though. Can you see if 

http://[fe80:0:0:a:38a4:ab5c:1610:8b33%253]:57492/Content/4AF364207FBF4F5272E5CFD325AF48CD1B134CF2-0.mkv

works with your setup? (the %3 encodes to %253)
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Fully fledged local media server sombrenote 0 481 04-17-2016, 12:50 PM
Last Post: sombrenote
  Invalid SOCKS cripples outbound communications, but everything's "OK" PlNG 0 1,711 10-28-2014, 12:17 PM
Last Post: PlNG



Users browsing this thread: 1 Guest(s)