mbland / custom-links

98%

master: 98%

LAST BUILD ON BRANCH fix-search-short-links

branch: fix-search-short-links

CHANGE BRANCH

x

Reset

• fix-search-short-links
• add-api-for-search
• add-okta
• alpine-fix
• api-json
• autocomplete-and-target-search
• autocomplete-api
• autocomplete-ui
• backend-delete
• bump-npms-and-dockerfile
• cc-test-reporter
• cla-#147
• codeclimate-token
• config-redis
• count-links
• count-to-clicks
• create-and-update-stamps
• create-click-handler
• create-link-view
• create-unknown-link
• deindex-and-reindex
• delete-link
• dialog
• dialog-data
• do-operation
• docker
• dockerize
• downcase-ids
• downcase-users-domains
• edit-link
• edit-link-nonfunctional
• edit-view-support
• empty-hash-view
• env-config-override
• extract-api-helpers
• extract-flash
• fix-error-response
• fix-smoke-test-flakiness
• fixups
• focus-element
• headless-chrome
• jsdoc
• launch-redis
• log
• make-api-call
• master
• migrate-autocomplete-target-url-indexes
• my-links
• my-links-buttons
• my-links-e2e
• my-links-landing-page
• readme
• redis-refactor
• redis-shutdown
• refactor
• remove-tabindex
• rename-location-to-target
• rename-redirectdb-to-linkdb
• rename-url-to-link
• save-on-exit
• search-links
• search-on-target-link
• search-ui
• show-timestamps
• show-view-handle-rejection
• show-view-promise
• stabilize-e2e
• style-touchups
• target-index-sets
• transfer-ownership
• travis-ci-fix
• update-npms
• update-packages
• urlp-to-cl
• v0.1.0
• v0.1.1
• v0.1.2
• v0.2.0
• v0.2.1
• v0.3.0
• view-and-backend
• wait-for-redis

Build # 683

Build Type

push

travis-ci

Committed by mbland

Commit Message

LinkDb: Fix searchShortLinks, return object

The first problem with the previous implementation (other than we forgot
to test it) was that the underlying RedisClient.searchShortLinks() was
already returning linkInfo objects. Consequently, the call to
RedisClient.fetchLinkData() was not only superflouous, but causing
server errors, because it expects an array of strings, not an array of
objects.

The second problem was that it returned an array, passed through the API
as a JSON array, which has presented various security vulnerabilities
over time (do a quick search on "json array security"). Wrapping arrays
in an object is still recommended by OWASP:

https://www.owasp.org/index.php/AJAX_Security_Cheat_Sheet#Always_return_JSON_with_an_Object_on_the_outside

Run Details

317 of 346 branches covered (91.62%)

Branch coverage included in aggregate %.

2872 of 2901 relevant lines covered (99.0%)

21.84 hits per line