Closed Bug 1038832 Opened 11 years ago Closed 11 years ago

Urls should not be shown in the call log for direct calls

Categories

(Hello (Loop) :: Server, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ferjm, Assigned: rhubscher)

References

Details

(Whiteboard: [qa+])

Attachments

(2 files)

Attached image 2014-07-15-19-07-26.png
No description provided.
This one's on the server side. We are getting the callUrl on a id to id call when we are not supposed get it: {"calls":[{"callId":"a87873b71470b54dc1f9f685ddfaa39f","callType":"audio-video","callerId":"ferjm@mailinator.com","websocketToken":"0a2685faccac3892ebcb8130f0d34b78","apiKey":"44669102","sessionId":"2_MX40NDY2OTEwMn5-U2F0IEp1bCAxOSAwNDoxNjo1MCBQRFQgMjAxNH4wLjg5NjA2MzI3flB-","sessionToken":"T1==cGFydG5lcl9pZD00NDY2OTEwMiZzaWc9MGRhNmRiZDEyZmNiZGZiMTk5ZGYwNWQ2OGZhZjMzZjdhYzM0NDM3ZTpzZXNzaW9uX2lkPTJfTVg0ME5EWTJPVEV3TW41LVUyRjBJRXAxYkNBeE9TQXdORG94TmpvMU1DQlFSRlFnTWpBeE5INHdMamc1TmpBMk16STNmbEItJmNyZWF0ZV90aW1lPTE0MDU3Njg2MDcmbm9uY2U9MC43NTQyMzI5NjEyMTg4MDQxJnJvbGU9cHVibGlzaGVyJmV4cGlyZV90aW1lPTE0MDU4NTUwMDc=","callUrl":"http://loop-webapp.dev.mozaws.net/#call/undefined","call_url":"http://loop-webapp.dev.mozaws.net/#call/undefined","progressURL":"ws://loop.dev.mozaws.net/websocket"}]} Note the "call_url":"http://loop-webapp.dev.mozaws.net/#call/undefined"
Component: Gaia::Loop → Server
Product: Firefox OS → Loop
Assignee: nobody → ferjmoreno
Attached file Link to github PR
Attachment #8459454 - Flags: review?(alexis+bugs)
Attachment #8459454 - Flags: feedback?(ferjmoreno)
Assignee: ferjmoreno → rhubscher
Status: NEW → ASSIGNED
Comment on attachment 8459454 [details] Link to github PR Thanks Rémy. I was just writing the tests for that very same fix.
Attachment #8459454 - Flags: feedback?(ferjmoreno) → feedback+
Comment on attachment 8459454 [details] Link to github PR Looks good, with nits addressed.
Oups :ferjm sorry about that I should have let you finish then :(
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Attachment #8459454 - Flags: review?(alexis+bugs) → review+
Where are these call logs located? I can verify the server-side changes, but how do we verify the call logs?
Whiteboard: [qa+]
Flags: needinfo?(ferjmoreno)
(In reply to James Bonacci [:jbonacci] from comment #7) > Where are these call logs located? > I can verify the server-side changes, but how do we verify the call logs? I suppose that with the Loop Mobile client application available in https://github.com/mozilla-b2g/firefoxos-loop-client
What :oteo said
Flags: needinfo?(ferjmoreno)
:natim Maybe I am missing something in the commit from Comment 6, but where are the changes to loop/index.js? This file appears to only have 188 lines in it now. Ah, so much has changed since July 21! I was able to verify the changes for test/functional_test.js.
James, `call log` here is the result of the API call to *GET /calls* With this fix we are making sure we don't return some information for direct calls that we want to keep for URL initiated calls.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: