Revisions to 'The target origin provided does not match the recipient window's origin' message when trying to use localhost

fixed typos and typesetting

Source Link

edit approved Mar 24, 2015 at 16:24

345
1
17

I faced the same issue when i was using the stack exchange API  to post a message to stack overflow website.
        
I figured I had to post my application on a domain name .I hosted my application on free domain provided by 000webhost.com .You may wish to take a similar approach .
    
After deploying the application on the domain , change the oauth domain and the application website on the app edit page .  Also , Keep in mind you have to link a valid stack apps post (a post made by you on stack apps) in the edit page .
    
This should work.

I faced the same issue when I was using the stack exchange API to post a message to stack overflow website. I figured I had to post my application on a domain name. I hosted my application on free domain provided by 000webhost.com. You may wish to take a similar approach.

After deploying the application on the domain, change the oauth domain and the application website on the app edit page. Also, keep in mind you have to link a valid stack apps post (a post made by you on stack apps) in the edit page.

This should work.

I faced the same issue when i was using the stack exchange API  to post a message to stack overflow website.
        
I figured I had to post my application on a domain name .I hosted my application on free domain provided by 000webhost.com .You may wish to take a similar approach .
    
After deploying the application on the domain , change the oauth domain and the application website on the app edit page .  Also , Keep in mind you have to link a valid stack apps post (a post made by you on stack apps) in the edit page .
    
This should work.

I faced the same issue when I was using the stack exchange API to post a message to stack overflow website. I figured I had to post my application on a domain name. I hosted my application on free domain provided by 000webhost.com. You may wish to take a similar approach.

After deploying the application on the domain, change the oauth domain and the application website on the app edit page. Also, keep in mind you have to link a valid stack apps post (a post made by you on stack apps) in the edit page.

This should work.

added 190 characters in body

Source Link

edited Feb 24, 2015 at 9:58

Can iSchool

31
4

    I faced the same issue when i was using the stack exchange API  to post a message to stack overflow website.
    
      
I figured I had to post my application on a domain name .I hosted my application on free domain provided by 000webhost.com .You may wish to take a similar approach .
    
After deploying the application on the domain , change the oauth domain and the application website on the app edit page .  Also , Keep in mind you have to link a valid stack apps post (a post made by you on stack apps) in the edit page .
    
This should work.

    I faced the same issue when i was using the stack exchange API  to post a message to stack overflow website.
    
     I figured I had to post my application on a domain name .I hosted my application on free domain provided by 000webhost.com .You may wish to take a similar approach .

After deploying the application on the domain , change the oauth domain and the application website on the app edit page .  Also , Keep in mind you have to link a valid stack apps post (a post made by you on stack apps) in the edit page .

This should work.

I faced the same issue when i was using the stack exchange API  to post a message to stack overflow website.
         
I figured I had to post my application on a domain name .I hosted my application on free domain provided by 000webhost.com .You may wish to take a similar approach .
    
After deploying the application on the domain , change the oauth domain and the application website on the app edit page .  Also , Keep in mind you have to link a valid stack apps post (a post made by you on stack apps) in the edit page .
    
This should work.

added 190 characters in body

Source Link

edited Feb 24, 2015 at 9:53

Can iSchool

31
4

    I faced the same issue when i was using the stack exchange API  to post a message to stack overflow website.
    
    I figured I had to post my application on a free domain name .I hosted my application on free domain provided by some000webhost.com sites.You likemay 000webhostwish orto herokutake a similar approach . 

After deploying the application on the domain , change the oauth domain and the application website on the app edit page . It willAlso work., ItKeep workedin formind meyou have to link a valid stack apps post (a post made by you on stack apps) in the edit page .

This should work.

I faced the same issue when i was using the stack exchange API  to post a message to stack overflow website.

I figured I had to post my application on a free domain name provided by some sites like 000webhost or heroku .After deploying the application on the domain , change the oauth domain and the application website on the app edit page . It will work. It worked for me .

    I faced the same issue when i was using the stack exchange API  to post a message to stack overflow website.
    
    I figured I had to post my application on a domain name .I hosted my application on free domain provided by 000webhost.com .You may wish to take a similar approach . 

After deploying the application on the domain , change the oauth domain and the application website on the app edit page .  Also , Keep in mind you have to link a valid stack apps post (a post made by you on stack apps) in the edit page .

This should work.

Source Link

created Feb 24, 2015 at 9:47

Can iSchool

31
4

Loading

Stack Exchange Network

Return to Answer