Search the Community
Showing results for tags 'http'.
-
One feature we LOVE about Dropbox and miss on BTSync is the ability to share a link to a single file that a user (not equipped with Dropbox) could open in their browser. I'm guessing your architecture makes this very difficult, even though you are providing a http server - I'm guessing that while I can access a client via http at for example http://192.168.1.34:8888/gui/ that this is not being exposed through UPnP/IGD and that therefore it would be hard to add the ability to retrieve files from its http server (in a similar way to Dropbox). Such exposure would be useful in other respects -
-
Request Headers. Note Accept. GET /api?method=get_folders HTTP/1.1Accept: application/jsonAccept-Encoding: gzip, deflate, compressAuthorization: Basic ASDFgfdsghstFDASGFDAGRADContent-Type: application/json; charset=utf-8Host: wintermute:8888User-Agent: HTTPie/0.8.0Response Headers. Note Content-Type. HTTP/1.1 200 OKCache-Control: no-cacheConnection: keep-aliveContent-Length: 654Content-Type: text/javascriptContent-Type should obviously be application/json -- we are not returning arbitrary JavaScript (aka JSONP) here. This should be fixed because: 1. sent content-type should match the reque
-
I work for a small research company that makes educational software/games, and we've got a deployment of 50 computers in 10+ schools. We're currently synchronizing our application and media content from our server to the schools, and our log files from the schools to our server using SyncBack (FTP, yes I know -- without the S, no need to lecture). The schools have varying and inconsistent firewall rules, so the sync isn't happening at some locations. I know the limitations of the networks and why the transfers aren't working, so I'm not asking how to get through the firewall limitations T