browser integration #52

New Issue

zooko · 2007-05-24T14:18:08Z

zooko commented

2007-05-24 14:18:08 +00:00

I want to load an HTML file from a grid and view it in my browser, and I want hyperlinks in that HTML file to cause other files to be loaded from the grid when I click on them.

Possible techniques:

proxy (the original technique used by Mojo Nation circa 1999)
Firefox plugin
reimplement Tahoe in JavaScript
?

I want to load an HTML file from a grid and view it in my browser, and I want hyperlinks in that HTML file to cause other files to be loaded from the grid when I click on them. Possible techniques: * proxy (the original technique used by Mojo Nation circa 1999) * Firefox plugin * reimplement Tahoe in [JavaScript](wiki/JavaScript) * ?

zooko added the

code

minor

enhancement

labels 2007-05-24 14:18:08 +00:00

warner added this to the undecided milestone 2007-07-14 07:00:04 +00:00

warner added

code-frontend-web

and removed

code

labels 2007-08-14 18:59:02 +00:00

zooko commented

2007-08-20 18:07:26 +00:00

This already works if your hyperlinks are of the form "http://localhost:${PORTNUM}" and have the right port number in them. Should we standardize on using a certain port number? If so, I suggest 8081 because it sounds webbish but isn't registered on the authoritative, canonical list of port numbers, wikipedia:

http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers

This already works if your hyperlinks are of the form "<http://localhost>:${PORTNUM}" and have the right port number in them. Should we standardize on using a certain port number? If so, I suggest 8081 because it sounds webbish but isn't registered on the authoritative, canonical list of port numbers, wikipedia: <http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers>

warner commented

2007-08-20 18:40:24 +00:00

unfortunately, standardizing the URLs like that (at least for the vdrive space) is in direct opposition to the XSRF issues from ticket #98. Outside attackers (who have vague control over the user's browser, in the form of serving them pages with IMG tags and deceptive hrefs and such) should not be able to control the local node.

On the other hand, having common URLs for reading URI-based resources shouldn't be a problem. (this also holds true for resources housed in the global vdrive, but the global vdrive is really a demonstration app rather than a long-term service).

unfortunately, standardizing the URLs like that (at least for the vdrive space) is in direct opposition to the XSRF issues from ticket #98. Outside attackers (who have vague control over the user's browser, in the form of serving them pages with IMG tags and deceptive hrefs and such) should not be able to control the local node. On the other hand, having common URLs for reading URI-based resources shouldn't be a problem. (this also holds true for resources housed in the global vdrive, but the global vdrive is really a demonstration app rather than a long-term service).

zooko commented

2007-08-23 19:57:12 +00:00

Now that we've solved #98, I think that the way we did it makes having a standard web-port number okay!

Having a standard port number would make it so that one person can cut-and-paste their URL and send it to their friend, their friend can paste it into the URL-editing-widget of their browser, and thus load up the same resource. Yay!

Now that we've solved #98, I think that the way we did it makes having a standard web-port number okay! Having a standard port number would make it so that one person can cut-and-paste their URL and send it to their friend, their friend can paste it into the URL-editing-widget of their browser, and thus load up the same resource. Yay!

zooko self-assigned this 2007-08-23 19:57:12 +00:00

zooko commented

2007-10-20 21:07:31 +00:00

As of v0.6.0, the default HTTP URLs start with "http://localhost:8123". This makes those URLs shareable among users who have Tahoe running locally.

It would be nice if someone who was using tahoe on a remote node, e.g. "http://mygateway.mydomain.org:8123" could click on a link given to them by someone running their locally, e.g. "http://localhost:8123"...

Any ideas on further improvements to this usability feature?

As of v0.6.0, the default HTTP URLs start with "<http://localhost:8123>". This makes those URLs shareable among users who have Tahoe running locally. It would be nice if someone who was using tahoe on a remote node, e.g. "<http://mygateway.mydomain.org:8123>" could click on a link given to them by someone running *their* locally, e.g. "<http://localhost:8123>"... Any ideas on further improvements to this usability feature?

zooko added the

0.6.1

label 2007-10-20 21:07:31 +00:00

warner modified the milestone from eventually to undecided

2008-06-01 20:53:36 +00:00

zooko commented

2008-11-17 00:46:40 +00:00

see also #432 (writing down filecaps: revise URI scheme)

davidsarah commented

2009-10-28 03:38:37 +00:00

Tagging issues relevant to new cap protocol design.

davidsarah commented

2010-01-01 03:43:16 +00:00

The default webapi port number was changed to 3456 by #536. Note Zooko's comment there, however:

the bigger issue is that each tahoe grid should use a different port number, so people should try not to rely on the default port number.

The default webapi port number was changed to 3456 by #536. Note Zooko's comment there, however: > the bigger issue is that each tahoe grid should use a different port number, so people should try not to rely on the default port number.

zooko modified the milestone from undecided to 2.0.0

2010-02-23 03:11:56 +00:00

zooko commented

2010-03-29 04:32:07 +00:00

Unassigning this from myself. We should probably make a new ticket specifically for the Firefox plugin idea. (Brian's new job is on Jetpack: https://jetpack.mozillalabs.com/ )

Unassigning this from myself. We should probably make a new ticket specifically for the Firefox plugin idea. (Brian's new job is on Jetpack: <https://jetpack.mozillalabs.com/> )

davidsarah commented

2010-03-29 23:49:45 +00:00

zooko wrote:

We should probably make a new ticket specifically for the Firefox plugin idea.

Yes, the summary of this ticket ("browser integration") is way too vague and unfocussed. The enhancement mentioned in the description, of being able to use a relative path from a directory cap to view a file in the WUI, was implemented many moons ago, leaving only the following issue from comment:60198 :

It would be nice if someone who was using tahoe on a remote node, e.g. <http://mygateway.mydomain.org:8123> could click on a link given to them by someone running their gateway locally, e.g. <http://localhost:8123>...

The ticket keywords for JavaScript-based UI are [jsui]query:status!=closed&keywords~=jsui (for Toby Murray's prototype, see #1000) and [webdrive]query:status!=closed&keywords~=webdrive (for the allmydata.com JS client, see #669). "Reimplementing Tahoe in JavaScript," OTOH, doesn't seem practical at this point.

zooko wrote: > We should probably make a new ticket specifically for the Firefox plugin idea. Yes, the summary of this ticket ("browser integration") is way too vague and unfocussed. The enhancement mentioned in the description, of being able to use a relative path from a directory cap to view a file in the WUI, was implemented many moons ago, leaving only the following issue from [comment:60198](/tahoe-lafs/trac-2024-07-25/issues/52#issuecomment-60198) : > It would be nice if someone who was using tahoe on a remote node, e.g. `<http://mygateway.mydomain.org:8123>` could click on a link given to them by someone running their gateway locally, e.g. `<http://localhost:8123>`... The ticket keywords for [JavaScript](wiki/JavaScript)-based UI are [jsui]query:status!=closed&keywords~=jsui (for Toby Murray's prototype, see #1000) and [webdrive]query:status!=closed&keywords~=webdrive (for the allmydata.com JS client, see #669). "Reimplementing Tahoe in JavaScript," OTOH, doesn't seem practical at this point.

tahoe-lafs added

unknown

and removed

0.6.1

labels 2010-03-29 23:49:45 +00:00

tahoe-lafs modified the milestone from 2.0.0 to 0.6.0

2010-03-29 23:49:45 +00:00

davidsarah commented

2010-07-20 04:47:25 +00:00

Including a grid identifier in URIs is #403. A browser plugin or protocol handler for Tahoe URIs is #1132.

tahoe-lafs added the

fixed