ericsson / c3-drop Goto Github PK

Currently only the first person opening the URL gets the file.

Ping @2trc 😄

#6
As a user, I want see the name/speed/rate/size of the file being transferred so that I can anticipate the time it will take and verify I have sent the right file.

Hello,

It seems that the certificate has expired. When I navigate to https://drop.cct.ericsson.net/ with Firefox I get the below:

Firefox detected an issue and did not continue to drop.cct.ericsson.net. The website is either misconfigured or your computer clock is set to the wrong time.

It’s likely the website’s certificate is expired, which prevents Firefox from connecting securely.

What can you do about it?

drop.cct.ericsson.net has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site.

Your computer clock is set to 5/7/2019. Make sure your computer is set to the correct date, time, and time zone in your system settings, and then refresh drop.cct.ericsson.net.

If your clock is already set to the right time, the website is likely misconfigured, and there is nothing you can do to resolve the issue. You can notify the website’s administrator about the problem.

Thanks,

F

Drag-n-drop file sharing does not working on mobile phones with touch interfaces.

Hi,

First of all, excellent job! Team members and I am quite excited to use the tool :)

As a suggestion for improvement, it would be excellent to have a way to limit access to Ericsson employees only (maybe via Erica certificates -- or login with SSO)

BR,
Dimple

As a user, I want a visual indication of the progress status of the transfer so that I can see how long the transfer will take and allow visual assurance and UI feedback on the action taken.

https://drop.cct.ericsson.net/#!wMNSrddUqIuassWSQX:webrtc-test-app

should be

https://drop.cct.ericsson.net/#!wMNSrddUqIuassWSQX

https://github.com/blog/273-github-ribbons

To reproduce:

1. Go to drop.cct.ericsson.net in Browser 1 (chrome || firefox)
2. Drop a big file (e.g 2GB)
3. Go to the link in Browser 2 (chrome || firefox)
4. Browser 1 crashes, Browser 2 doesn't see any progress.

This only happens for big files. 700MB worked fine, 2GB did not. WebRTC logs didn't show anything interesting, so it's probably related to the way the file is loaded into memory (possibly an SDK problem).

Chrome will preserve the original filename, even across networks, but the received file in Firefox is named as 8 random characters with only the filetype preserved (e.g., data.xlsx is received as x5ibefqt.xlsx).