<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">

 
 
  <channel>
    <title>Content-Type on ServiceNow Developer Blog</title>
    <link>https://developer.servicenow.com/blog.do?p=/tags/content-type/</link>
    <description>Recent content in Content-Type on ServiceNow Developer Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 12 Jul 2017 16:57:00 +0000</lastBuildDate>
    
        
        
         
        <atom:link href="https://developer.servicenow.com/blog.do?p=/tags/content-type/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Accepting Scripted REST Connections for Weird Content-Types</title>
      <link>https://developer.servicenow.com/blog.do?p=/post/accepting-scripted-rest-connections-for-weird-content-types/</link>
      <pubDate>Wed, 12 Jul 2017 16:57:00 +0000</pubDate>
      
      <guid>https://developer.servicenow.com/blog.do?p=/post/accepting-scripted-rest-connections-for-weird-content-types/</guid>
      <description>In an interesting coincidence, I recently had to solve this issue in my own Travel Tracker app (as seen on a number of Live Coding Happy Hour episodes). Just today, someone in the Developer Program asked the same thing so I thought I would document it for posterity. What happens when an incoming connection you don&amp;rsquo;t control (such as a webhook) isn&amp;rsquo;t using application/json or application/xml as the Content-Type on the HTTP transaction?</description>
    </item>
    
  </channel>
</rss>