search

cu-mkp / fieldnotes-restructuring

0 stars 0 forks source link

S3 urls vs. actual working ones (character encoding problems) #9

Closed njr2128 closed 3 years ago

njr2128 commented 3 years ago

certain URLs with special characters (particularly spaces, etc) will be handled one way by S3 but another way when actually accessed as a webpage. For example:

In S3: fieldnotes.makingandknowing.org/mainSpace/David%C2%A0McClure+-+Field+Notes+FA15.html (notice + for spaces) -- this does not work if you follow the link (404 error)

To actually access the page: http://fieldnotes.makingandknowing.org/mainSpace/David%C2%A0McClure%20-%20Field%20Notes%20FA15.html (spaces are represented as %20)

njr2128 commented 3 years ago

This seems to be due to how S3 handles special characters - it automatically changes spaces to + --> perhaps this can be changed on a higher level for how the bucket handles this.

But in the meantime, we discovered that the URL proper IS put in the bucket, with the file name and now encoded characters (we had previously ignored this because I thought it was not a valid URL because of the spaces): image