You can still browse the source archive at <a href="https://repo.aalto.fi/index.php?name=SO_b66a9391-dcf8-4399-8e87-611f84c3fc4c" rel="nofollow">https://repo.aalto.fi/index.php?name=SO_b66a9391-dcf8-4399-8...
dang - if the source archive is the same as the submitted URL, then this would probably be a better URL to use in this posting which is returning an error for me and a number of other users
HN mods [*generally] don't magically appear here when mentioned (unless you do it three times in a mirror while sacrificing DRAM), but they are absurdly responsive when contacted via hn@ycombinator.com.
Are you saying we should change the link at the top to <a href="https://repo.aalto.fi/index.php?name=SO_b66a9391-dcf8-4399-8e87-611f84c3fc4c" rel="nofollow">https://repo.aalto.fi/index.php?name=SO_b66a9391-dcf8-4399-8...? I'm a bit unclear...
Edit: I've changed to that from the submitted url (<a href="https://nokiadesignarchive.aalto.fi/index.html" rel="nofollow">https://nokiadesignarchive.aalto.fi/index.html) for now, since that one was 403ing.
It seemed to be struggling earlier, perhaps it has hit some sort of bandwidth quota and the error response is an unhelpful 403.
I've seen that before, perhaps it counts as unauthorised because the server is not authorised to send when the quota is breached?. It isn't correct use of 403 (which implies the server knows the identity of the user, 401 is the more general state for unauthorised. Of the standard responses 503 (Service Unavailable) seems most correct.
(we've changed the url - more at <a href="https://news.ycombinator.com/item?id=49833578">https://news.ycombinator.com/item?id=49833578)
thedays · · focus · HN ↗
Aalto University web hosting service
nokiadesignarchive.aalto.fi
403 Forbidden
Access denied by server configuration and/or resource permissions.
Piko · · focus · HN ↗
eyeundersand · · focus · HN ↗
zczc · · focus · HN ↗
[deleted] · · focus · HN ↗
[deleted]
thedays · · focus · HN ↗
CharlesW · · focus · HN ↗
dang · · focus · HN ↗
Are you saying we should change the link at the top to <a href="https://repo.aalto.fi/index.php?name=SO_b66a9391-dcf8-4399-8e87-611f84c3fc4c" rel="nofollow">https://repo.aalto.fi/index.php?name=SO_b66a9391-dcf8-4399-8...? I'm a bit unclear...
Edit: I've changed to that from the submitted url (<a href="https://nokiadesignarchive.aalto.fi/index.html" rel="nofollow">https://nokiadesignarchive.aalto.fi/index.html) for now, since that one was 403ing.
dspillett · · focus · HN ↗
I've seen that before, perhaps it counts as unauthorised because the server is not authorised to send when the quota is breached?. It isn't correct use of 403 (which implies the server knows the identity of the user, 401 is the more general state for unauthorised. Of the standard responses 503 (Service Unavailable) seems most correct.
dang · · focus · HN ↗