Opened 17 years ago
Closed 17 years ago
#11 closed defect (fixed)
links from using-foolscap broken; "private" should be "public" in context of tubID
Reported by: | arch_o_median | Owned by: | Brian Warner |
---|---|---|---|
Priority: | minor | Milestone: | 0.1.6 |
Component: | documentation | Version: | 0.1.5 |
Keywords: | Cc: |
Description
At least _some_ links out of the using-foolscap.html page give "404 No Such Resource" errors. There are several references to "private" that should be "public" e.g. "SSL private key certificate" in the "Making your Tub remotely accessible" section should be say "SSL public key".
Change History (4)
comment:1 Changed 17 years ago by
Component: | unknown → documentation |
---|
comment:2 Changed 17 years ago by
Owner: | set to Brian Warner |
---|---|
Status: | new → assigned |
comment:3 Changed 17 years ago by
Milestone: | undecided → 0.1.6 |
---|
comment:4 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I've fixed the API doc links. I think that's the last of them: if you see others, please open up a new ticket.
Note: See
TracTickets for help on using
tickets.
I applied the patch from zooko to address the private-vs-public certificate issue.
Which links are giving you 404s? There are a lot of lore-generated links to API docs that refer to non-existent sibling pages like foolscap.schema.ListOf? and foolscap.Violation . I need to add a target to build those, I've created #16 to track this issue.
Are there other broken links? Specifically ones that point to other sites?