Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Allow accessing content at /api/content/<hash> #2245

Closed
tomusdrw opened this issue Sep 22, 2016 · 0 comments
Closed

Allow accessing content at /api/content/<hash> #2245

tomusdrw opened this issue Sep 22, 2016 · 0 comments
Assignees
@tomusdrw
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.

Comments

@tomusdrw
Copy link
Collaborator

Same logic that currently works for localhost:8080/<hash> and <hash>.parity
@tomusdrw tomusdrw added P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. labels Sep 22, 2016
@tomusdrw tomusdrw self-assigned this Sep 22, 2016
@tomusdrw tomusdrw mentioned this issue Sep 22, 2016
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tomusdrw tomusdrw

Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomusdrw