404 not found error without https:// when type https its working fine cloudflare problem i think - http-status-code-404

when i type http://profilepics.in its my website i am getting 404 not found error. Here is the link : https://profilepics.in/error-page.jpg.
When i type https:// its working fine. I am using cloud flare please help me to get rid of this.

Related

react native 404 not found while using deployed endpoint

I'm using React Native to work on my project. The problem I'm facing: it is working perfectly 200 ok while fetching data locally but, when I try to use after deployment it says 404 not found.
What could be the reason?
A 404 error is an HTTP status code that means that the page you were trying to reach, couldn't be found on their server.

React/Github-pages: Failed to load resource: the server responded with a status of 404 ()

I have successfully uploaded react app`s to github pages before, but this time when I try to upload a new page the code is pushed and everything looks fine in the repository, everything loads fine in the localhost. The problem is when I access the website in the console i get the error message above.
const res = await axios.get(' https://api.open5e.com/monsters/?limit=1086');
I am using this API, the limit is above 50 but I don`t believe this is the reason for the crash but I cannot think of anything else.
Website 1: (Currently redirects you to a 404 error page, as part of my attempt to solve the problem)
https://ottotsuma.github.io/MonsterSearch/
Repo - Website 1:
https://github.com/ottotsuma/MonsterSearch
Website 2:
https://ottotsuma.github.io/MonsterApiReact/
Repo all code:
https://github.com/ottotsuma/DnD-React
I also get this error in localhost and the hosted website: Uncaught TypeError: Cannot use 'in' operator to search for 'default' in undefined. But since the website was working as intended so far I have just ignored it.
I was hoping if anyone else has had a similar problem with gh-pages they might know what I have done wrong.
Kind regards,
Sheep

Autodesk Forge API tutorial Get a 3-Legged Token 404 error

I have a similar issue to this post.
I am following the 3-legged tutorial on the Forge API website here, and I matched the callback URI and URL, tried swapping the data:read for viewables:read, and tried switching to https:// and not http:// but I'm still getting an error when I run the app and login via the link in the tutorial which I adjusted with my information.
The error I get is:
Not Found.
The requested URL /parking/oauth/callback was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Do you know what could be wrong?

The requested URL was not found on this server in cordova for the facebook plugin in react?

i actually used the facebook login npm in react and i tried on my browser it works when i run on ios devices using cordova,it shows the following error
Failed to load webpage with error: The requested URL was not found on this server.
i don't know how to fix this? can anyone help me.here my samples
<FacebookLogin
appId="XXXXX682921631"
language="en_US"
scope="public_profile,email"
callback={this.responseFacebook}
xfbml={true}
fields="id,email,name"
cookie={true}
version="v2.10"
className="facebook-login"
textButton="Login With Facebook"/>
and i use my http://localhost:8080/ it works on browser and i ain't know about the mobile what to give and where to give

GAE google task api "Error: Not Found"

I have followed this google task api tutorial on GAE: https://developers.google.com/appengine/articles/python/getting_started_with_tasks_api
I have tried everything they did.
I have added this in the route:
('/mytask', mytask),
('/mytask'+ decorator.callback_path, decorator.callback_handler()),
yet I am getting following error:
Error: Not Found
The requested URL /oauth2callback?state=http://sadaf2605.appspot.com/mytask:rBFVjEpyDnAPoYsm-J6COToxMzY1NDM0ODg4&code=4/DVdE2clKgg1yfLTcFL9AdGzszVvj.snlDhp_QkQYZgrKXntQAax1q0onUewI was not found on this server.
Can you guys please tell me where can I expect a bug?
You're not attaching the handler to the right URL: you're prefixing it with '/mytask'. If you don't want it to serve on the default /oauth2callback, then you need to pass callback_path when you create the OAuth2Decorator

Resources