erotix / phone2chrome

Automatically exported from code.google.com/p/phone2chrome
0 stars 0 forks source link

URL field in Dropbox includes elements from title, etc. #22

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Share a link from a phone, seems like links from Twitter clients are most 
likely to show this.
2.Try to view it from Chrome, and notice it puts up a not found error. 
3.View the Dropbox file and find the URL contains lots of human readable stuff 
that can't possibly work. 

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
Don't see any version reported on Android app. Android is 2.3.5. 

Please provide any additional information below.

Now I have the opposite problem from the truncation at '?' reported in #17 and 
#18! The URL field is getting too much information:

    {
      "date": 1400691713468,
      "url": "http:\/\/arxiv.org\/abs\/1405.3760 | PIN Skimming: Exploiting the Ambient-Light Sensor in Mobile Devices\narxiv.org\/abs\/1405.3760 \n#WTF",
      "title": "Tweet from @semibogan : "
    },
    {
      "date": 1400692884424,
      "title": "Tweet from @emilycrockett : ",
      "url": "http:\/\/t.co\/miIcTi7leY | This is really just the best thing. What if we admitted to our children that sex is about pleasure? t.co\/miIcTi7leY"
    }

The human readable title of the linked site is going into the URL field, 
followed by a repeat of part of the URL. Obviously Chrome can't go there... 

Those two links are from the Falcon Pro Android Twitter client. 

But it also happens from Plume:

    {
      "date": 1399218379215,
      "url": "This spectacularly smart infographic uses #irony to promote the idea of #rainforest #biodiversity #conservation http:\/\/twitter.com\/FisherSpeaks\/status\/461217225660039168\/photo\/1\n\nhttps:\/\/twitter.com\/FisherSpeaks\/status\/461217225660039168\n\nShared via Plume\nhttp:\/\/bit.ly\/GetPlume",
      "title": "Tweet from Chris Fisher (@FisherSpeaks)"
    },

This looks like the first occurrence of this problem for me:
Thu, 17 Apr 2014 17:10:58 GMT
    {
      "date": 1397754658317,
      "title": "Check this picture",
      "url": "http:\/\/pbs.twimg.com\/media\/BlbJSsLCAAEhu00.jpg:medium\nFrom this tweet:\nBanksy back in action: huff.to\/1jMZM97 pic.twitter.com\/sS4JxDuouZ"
    },

Did the code change about then? 

Original issue reported on code.google.com by LorenAme...@gmail.com on 21 May 2014 at 7:43