Bug 127957 - FIX URL behavior for out of range port numbers
Summary: FIX URL behavior for out of range port numbers
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 128023
  Show dependency tree / graph
 
Reported: 2014-01-30 15:04 PST by Maciej Stachowiak
Modified: 2023-08-23 00:20 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Stachowiak 2014-01-30 15:04:12 PST 
FIX URL behavior for out of range port numbers
Comment 1 Anne van Kesteren 2023-08-23 00:20:22 PDT 
From our text expectation files:

PASS URL: Setting <http://example.net:8080/path>.port = '65536' Port numbers are 16 bit integers, overflowing is an error
PASS URL: Setting <http://example.net:8080/path>.port = 'randomstring' Setting port to a string that doesn't parse as a number
PASS URL: Setting <non-special://example.net:8080/path>.port = '65536' Port numbers are 16 bit integers, overflowing is an error