Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

Parse - 403 Forbidden
Started by Nerox Nov 01 2018 11:38 AM

2 replies to this topic
[TOPIC CONTROLS]
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

Nerox

[GLOBAL: userInfoPane.html]
Nerox
  • Enthusiast

  • 96 posts
  • Corona SDK

I have been using and developing an app for some months now, I've been using the Parse plugin (back4app as parse solution), It has been working well for months, but yesterday out of the blue any parse request always returns an error (HTTP-STATUS-LINE: HTTP/1.1 403 Forbidden) I've made sure all my keys are correct, and that I should be authorized, but still the error occurs, I made a try to call the request myself using network.request and IT WORKED, ??!!! So when I send the request using network.request it works but when I send it using parse plugin it returns the above error.

Note: last time the plugin was updated was a long time ago, I haven't changed anything that would cause this and to make sure that the problem wasn't from my code I made a new project from scratch to test if the error still occurs and it still occurs.

I have tried from another pc and the problem still occurs.

I have tried from another internet and the problem still occurs.



[TOPIC: post.html]
#2

Nerox

[GLOBAL: userInfoPane.html]
Nerox
  • Enthusiast

  • 96 posts
  • Corona SDK

I've opened the source files of the plugin and tried to track the problem, I found that in the file "request.lua"

if I remove these lines (263, 264) which are the params body of the network.request and the Content-Length header the problem is fixed, I am not sure what are these, but still I don't know why it got broken in the first place and still don't know how to fix my problem, I cannot update the plugin should I just grab the source files and include them in my app ?

https://bitbucket.org/develephant/corona-plugin-parse/src/e1ced84c390eacb0691c2a1d18998efe2c12844b/lua/plugin/parse/request.lua?at=master&fileviewer=file-view-default



[TOPIC: post.html]
#3

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 24,860 posts
  • Corona Staff

You could do a pull request to send your changes back to @develephant and he can choose to add them back to his repository. Likely something changed on your server end that's incompatible with the way your plugin is working. So grabbing the source and using it would likely be your best course of action.

 

Rob




[topic_controls]
[/topic_controls]