I’m out of my depth with these error messages that have been popping up in my TYPO3 log for a couple of weeks now, sometimes loads of them within just a couple of minutes.
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1436717322: The parsedUri "https:///" appears to be malformed | InvalidArgumentException thrown in file /.../typo3_src-11.5.22/typo3/sysext/core/Classes/Http/Uri.php in line 125. Requested URL: https:///
[edit of the original post, following notes in the comments]
The TYPO3 log file showed the following expanded message:
Tue, 31 Jan 2023 13:15:22 +0000
[CRITICAL] request="7331e1d6281d8"
component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB: BE): InvalidArgumentException, code #1436717322, file /path/to/typo3_src-11.5.22/typo3/sysext/core/Classes/Http/Uri.php, line 125: The parsedUri "https:///" appears to be malformed -
{"mode":"WEB","application_mode":"BE","exception_class":"InvalidArgumentException","exception_code":1436717322,"file":"/path/to/typo3_src-11.5.22/typo3/sysext/core/Classes/Http/Uri.php","line":125,"message":"The parsedUri \"https:///\" appears to be malformed","request_url":"https:///","exception":null}
[edit end]
The actual parsedUri value differs and can be something like https:///index1.php or https:///aspnet_client, and many others.
I have no idea how something like this can be sent to the TYPO3\CMS\Core\Http\Uri class, and neither do I know how to find a stacktrace of this exception so that I could try and reproduce what leads to it.
There is a docs entry for the exception which also doesn’t help me.
In my typo3conf/sites/[my-website]/config.yaml I have defined the base:
websiteTitle: 'My Website'
base: 'https://www.my-web.site/'
I would like this to end. To me they look like attempted attacks and even though they are apparently blocked, they might lead to something more serious and they do clutter my log obscuring other entries I might want to tackle.
Related
I posted a question on this yesterday to the GitHub support page and it got flagged as a duplicate - the original answer is here. This issue doesn't automatically fix like it did for that user. Instead, it seems to come and go with no pattern, so I don't have a good way to replicate it. Some songs will work at one point in time, then they won't a couple minutes later.
Error:
[debug] Encodings: locale cp1252, fs utf-8, out UTF-8, pref cp1252
[debug] youtube-dl version 2020.09.20
[debug] Python version 3.7.8 (CPython) - Windows-10-10.0.19041-SP0
[youtube:search] query "iron man 3 song": Downloading page 1
[debug] exe versions: none
[debug] Proxy map: {}
ERROR: query "song name": Failed to parse JSON caused by JSONDecodeError('Expecting value: line 1 column 1 (char 0)')); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see https://yt-dl.org/update on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
I get the issue when attempting to extract the data from the video. Here is a snippet of the code I am using:
ydlOps = {
'format': 'bestaudio/best',
'outtmpl': './%(title)s.webm',
'noplaylist': True,
'extractaudio': True,
'audioformat': 'webm',
'default_search': 'ytsearch1',
'quite': True,
'verbose':True,
'version': True
}
with youtube_dl.YoutubeDL(ydlOps) as downloader:
songData = downloader.extract_info(url, download=download)
I have changed the options, tried other options said to have worked, and nothing seems to make a difference. Some will work, then not, then they will again.
I think this is a youtube-dl bug. I wrote a parser for youtube searches and it also broke.
When looking previously at the response from youtube, all the JSON data was stored like this:
window["ytInitialData"] = {...}
So you just had to search through the server's response for the string 'window["ytInitialData"]' to find the relevant JSON and extract it. But now, youtube stores the JSON like this inside the html file sent by the server
var ytInitialData = {...}
This needs to be changed on youtube-dl's part when parsing the results.
What's strange is that sometimes youtube uses the previous version and sometimes it uses the current one. I think it's because the change in javascript is progressively being rolled out accross all youtube servers.
Also note that now, the line containing all the JSON ends with '; ' instead of just ';'. This might also require a change from youtube-dl.
You need to submit a pull request to youtube-dl or wait for somebody to fix it.
WAK 1.1.3 - during solution load, get a backend error:
[Backend] Error
[Backend] SyntaxError: JSON Parse error: Unexpected EOF
But it is not clear what file has this issue. How to most efficiently isolate this? I see nothing in the logs. The application has been running stably. I assume this is in a method, but am not finding it after a thorough search.
Thanks for guidance.
Kirk
Unexpected EOF error could be as small as forgetting to close function body with a right curly bracket.
I recommend first checking all the code on the backend you have modified since the last successful restart.
Secondly, since this occurs during solution load, the error is likely in bootstrap code including login listener. Or in model.js. You could try comment out all code in bootstrap.js or model.js see if the solution can load.
I downloaded the project sample CustomerManagement-AutoViews from this location.
After performing the necessary setup mentioned on the same url to build the solution, I still get a bunch of error related to resource not found when I build the project.
All the error description says
CustomerManagement.AutoViews.Droid.Resource.Layout' does not contain a
definition for
'dialog_textfieldright' C:\Users\\Documents\GitHub\MvvmCross-Tutorials\Sample
- CustomerManagement\CustomerManagement - AutoViews\CustomerManagement.Droid\Resources\Resource.Designer.cs 70 127 CustomerManagement.AutoViews.Droid
Am I missing something here?
I had created one wordpress site.
It was working nicely but now it showing the error as follows :
Warning: Cannot modify header information - headers already sent by (output started at /home/**/public_html/wp-content/themes/**/includes/classy-options-init.php:1) in /home/*/public_html/wp-includes/pluggable.php on line 866
What is exact problem please help me.
Read up on how to go about troubleshooting this extremely generic error message:
https://wordpress.org/support/article/faq-troubleshooting/#how-do-i-solve-the-headers-already-sent-warning-problem
Again, this message gives us virtually nothing to work with. Aside from the line # in pluggable.php, the question might as well read "this doesn't work". Try googling for "pluggable.php on line 866" to see some likely causes, since that's all you have to go on at the moment.
Additionally, take a look at your web server (apache?) error logs, and see if you get any more info out of them.
Finally, take a look at other questions involving pluggable.php on SO. They may or may not be a dupe of this issue. For example:
Cannot modify header information - headers already sent by... WordPress Issue
I have two orchestrations One of them is used as an error handler for the other orchestration, and is getting failed messages from it. I have set this up in BAM. The problem is when a file fails in the receive port I don't get any useful information in the Activity Search. Only that something has been registered. Data ex from BAM:
ActivityID: 2738a492-04c7-4887-9ff3-6902f435bda4
ErrorCode:
ErrorDesc:
Filename:
Progress Error: Handled
TransactionId:
rcvPort:
sndPort:
In the tracking profiler I use the properties from the errorReporter. Ex ErrorReport.FailureCode. The file gets moved as it should by the Error handler orchestration.
Does someone now what I'm doing wrong?
Is it possible to get any information when a file fails in the receive stage?
Mostly I need the filename and the error code/desc. (the Progress Error is a progress activity I have created).
I worked it out. For some reason I couldn't trace it to bam if I made progress dimension for the messages. When I just stored the plain data it worked ok.