GQ
02/18/2026, 12:58 AMCeligo AI
02/18/2026, 12:58 AMAI generated answer (using internal Slack threads):****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** From the conversations, it appears that you're trying to access the
Set-Cookie headers from an HTTP request in a server-side SuiteScript. Unfortunately, the NetSuite https module only provides access to the first Set-Cookie header in the response. This is a limitation of the NetSuite https module and there's no direct way to access the rest of the cookies that the server returned.
As for calling a Suitelet from a UserEventScript, it's important to note that internal Suitelet URLs require the client to be logged into NetSuite, or at least to send a valid JSESSIONID cookie. If the Suitelet is not available without login, you might need to consider making your Suitelet public or using your Suitelet script in a UserEvent as an import library and invoking it.
Regarding the issue with calling an external API like SmartyStreet from a NetSuite online customer form and getting a 401 or 405 status code, these are not CORS issues. A 401 error indicates unauthorized access, while a 405 error indicates that the method you're trying to use is not allowed. You might need to use SuiteScript and the N/https module to work around these issues.Celigo AI
02/18/2026, 12:58 AMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.815857053
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.804016113
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.797912598
Celigo AI
02/18/2026, 12:58 AM