# Webdev Module and AJAX

**URL:** <https://forum.inductiveautomation.com/t/webdev-module-and-ajax/17073>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [February 21, 2018, 3:15pm UTC](https://forum.inductiveautomation.com/t/webdev-module-and-ajax/17073 "2018-02-21T15:15:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\
**Post date:** [February 22, 2018, 7:16am UTC](https://forum.inductiveautomation.com/t/webdev-module-and-ajax/17073/2 "2018-02-22T07:16:17Z")

</div>

This post will probably help:

> [@Web Dev Response Headers](http://forum.inductiveautomation.com/t/web-dev-response-headers/11577):
>
> I’m wondering if there’s a way to manipulate the response headers of a doGet method in the Web Dev module. I need to add ‘Access-Control-Allow-Origin’ to the headers of the response object to allow other domains/servers/sites access to the end points. Javascript has built in security restraints (CORS) to guard against Cross Site Scripting. This is usually negated by adding Access Control in the header response. I know my code is working because I can easily get the data when consuming the end p…

---

_[View the full topic](https://forum.inductiveautomation.com/t/webdev-module-and-ajax/17073)._