When I tried accessing my GAE app today the server said that it couldn't find the static HTML file I wanted; it had been working fine yesterday, and I hadn't made any changes to appengine-web.xml or web.xml. The GAE logs say No handlers matched this URL. for the static files.
[Irrelevant details removed]
Stupid me, I had changed appengine-web.xml; specifically, I'd removed <include path="**"/> from the static-files section. Putting that back in fixed the problem.
Related
I have the following problem:
After trying to change the entry point to my website in the backend of my TYPO3 system (by using the site config), I cannot access neither my backend nor my frontend of the website anymore. Whenever I try to access the site it says "Oops, an error occurred! The parsedUri "https://" appears to be malformed".
What I have tried, is accessing the config.yaml on my webserver to change the baseURL inside of the config, but no matter what I change it to, it doesn't seem to work, as I always get the same error message even uploading the changed config file (what I mean by that is, that the text inside the error message doesn't change to reflect the new url but stays "https://").
I hope that someone who is more experienced in TYPO3 can help me solve this issue. I couldn't really find a working solution after extensively searching so far. Thanks a lot in advance.
After changing the yaml file of the site configuration, you need to clear all caches, either via the install tool (yourdomain.tld/typo3/install.php) or by deleting all files in the directories var/cache/code and var/cache/data.
Strangely, I am unable to deploy flutter apps via Flutter web since some days.
I have not problem running and debugging the Flutter app in a chrome browser via Android studio but once I try
flutter build web
the generated index.html file unter /build/web/ will show a blank page with these errrors:
Chrome error messages image
I started a completely new project so the error will not be due to my bad code writing :P
Can somebody help?
just change to <base href="./"> in index.html after you build the web.
Try remove .dart-tool folder in your project folder and rebuild your projcet.
I had the same error and changing index.html not worked. I solved it by removing .dart-tool folder in your project folder. After removing it, IDE shows some errors but flutter build web works fine.
Here is the origin link. https://github.com/flutter/flutter/issues/61464#issuecomment-924577391
just Clear browsing data in privacy and security
if not see any error in the console
This is an old question, but it seems to perpetuate (I also crashed into it). So here is what helped me to solve the problem:
The doc says:
Update the <base href="/"> tag in web/index.html to the path where your app is hosted.
In my case, it was htdocs/app, so base href become <base href="/app">, which fix the problem for me.
I have read other posts with people having issues with the 404 Not Found error when building their own local version of NuGet.Server. None of them specifically asked about what I am seeing as an issue.
I followed the instructions at https://learn.microsoft.com/en-us/nuget/hosting-packages/nuget-server and get the Default page just like it said. The only changes I made to the web.config were to set the requireApiKey=false since this will be a local server.
When I click on the "Click Here to View Packages", and get the 404 Not Found error, I noticed something on the page. It looks like it is trying to resolve to the same URL that is shown as the link for the Package Manager (https://localhost:44375/nuget), but then adds "Packages". Which might seem okay until you look at the "Physical Path" that is listed. It has a physical folder called "nuget" which is not there and was never created in the instructions or during the install of the NuGet.Server package.
Here is a screenshot of the 404 page.
There was nothing in the documentation about adding that folder, and it was not added when NuGet.Server was installed. Is this a configuration issue that I cannot seem to find, a setup step missed in the instructions or a bug in the NuGet.server ?
on a particular page on our site http://www.sakshum.org/ui/page/JoinUs.jsp which is build using gwt and deployed on GAE the module does not load.
This works fine in development env in eclipse and have no errors when looking via firebug in the console.
Please advise what may be wrong here and how to fix it?
look at the AE logs. firebug will only show you client side stuff. It's probably a classpath issue -- such as you have something locally but aren't uploading that jar ...etc.
Edit:
please post your JoinUs.jsp
I am calling my gwt module via a jsp page on AE no problem. Maybe the path in your script tag pointing to the *.nocache.jsp file is off somehow. Usually when things resolve locally but not on AE, for me, the problem was appengine-web.xml and setting include and exclude paths. I had to be careful there because things worked differently locally and deployed - especially using wildcard.
Also, look for uri errors under the dashboard (ae administration page). static resources that are not found will show there and not in the ae log since they are static.
Thanks all for the help. So, the issue was completely different. Actually the div tag was not rendering at all due to the coding error of a if statement in the jsp. On fixing that it started working
I am using Eclipse for Android dev and everything was going fine until I tried to incorporate the facebook SDK. Now when I tried to back it out, there appears to be an artifact left behind that Eclipse tries to link the FB library?!?
[2010-11-17 18:50:22 - Library Project] Unable to set linked path var '_android_com.facebook.android' for library /Users/mobibob/Projects/workspace/facebook-android-sdk/facebook: Path variable name cannot contain character: ..
Any clue where this command / reference is in the build configuration? I have scoured it as best that I can, but I still get the same error.
Problem solved ... as it turns out, it was not so much the Facebook SDK but something that I did in the process of configuring the library reference. I am not entirely certain of how I misconfigured, but I was tweaking the various "path" settings such that, once when the automatic build tried to build my project, an import for android.R was added to my source module. This superseded com.myproject.R and would not resolve the values for resource references.
There were other problems with path order and setting that I modified during the troubleshooting that made it worse. Recreating the project without Facebook was the first step to discovery and fixing.
Either way, the lesson I learned is that the build error messages can misdirect one to the configuration when the problem is in the source code.