Reject printers with invalid uri when parsing JSON.
Previous behavior was to accept the uri and CUPS would reject it when we try to use it. Received a report of this happening in TT. This will help to surface the root cause for users. Bug: 844521 Change-Id: I77a20232a7317ee40c7c3c0fa534d73d9aad2b4b Reviewed-on: https://chromium-review.googlesource.com/1066392 Commit-Queue: Sean Kau <skau@chromium.org> Reviewed-by:Xiaoqian Dai <xdai@chromium.org> Cr-Commit-Position: refs/heads/master@{#560912}
Showing
Please register or sign in to comment