Discussions
Changes to SuiteScript’s Handling of HTTP Request Header Names
| [TABLE="border: 0, cellpadding: 0, cellspacing: 1, width: 722"] [TR] [TD] [TABLE="border: 0, cellpadding: 0, cellspacing: 0"] [TR] [TD] [IMG2=JSON]{"data-align":"none","data-size":"full","src":"http:\/\/netsuite-info.com\/core\/media\/media.nl?id=1859026&c=NLCORP&h=7354131dbf70edf728ac&_od=aHR0cHM6Ly9zeXN0ZW0ubmV0c3VpdGUuY29t"}[/IMG2] |
| [TABLE="align: center, cellpadding: 1, cellspacing: 0"] [TR] [TD] [TABLE="align: center, border: 0, cellpadding: 0, cellspacing: 0"] [TR] [TD="width: 100%"]As of 2017.1, NetSuite is planning changes to the way SuiteScript handles the names of HTTP request headers. Historically, SuiteScript has required an exact case-sensitive match to identify header names. In the future, this handling will change. This change is being made to align SuiteScript with the HTTP specification. The effects of these changes vary depending on the version of SuiteScript and the method being used. Review this notification, and update your scripts as appropriate. |
Regards,
@Robert Nedelkow-Oracle | NetSuite Support Community Administrator
Save the date: Join us for invaluable insights from ADMINISTRATION/CRM expert Mich Jabanes this coming NOVEMBER 19, 2025 - 1:00 PM TO 2:00 PM EST for Ask A Guru Live. RSVP and follow #AskAGuruLive for insights.
In case you know someone who is new to NetSuite, we encourage you to direct them to our newly launched "New to NetSuite" page. This page is specifically designed to offer them information and guidance and help them make the most out of their NetSuite journey. Click here for more details.
