René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"cannot read opcode 0x0, but next byte is a string opcode","articleBody":"Attached you'll find a charles proxy dump of a session which is basically a Session object serialized.\nI'm trying to load this in so I can read it in a python-way.\n\nHowever, I think the reader is wrong somewhere because when your library wants to read `alpnProtocol`, it fails with `RuntimeError(\"Unknown OpCode in the stream: 0x0 (at offset 0x967)\")`. But when going to check the actual binary data, I can see the next byte is 0x74 (string-opcode).\n\nSo my best guess is that the reader peeked somewhere and didn't advance the file pointer?\nOr that a certain object has a 0x0 \"closing opcode\" or so?\n\nI hope you could have a look at this and fix the issue at hand.\n\n[github.zip](https://github.com/user-attachments/files/20650125/github.zip)\n\n\u003chr\u003e\nEDIT1: when checking the code, I saw that `\"actualPort\"` was a very weird number, so I advanced the file pointer. And lo-and-behold, the `actualPort=443`. So the filepointer is already wrong there.\n\u003chr\u003e\nEDIT2: I think I found the place:\n\n```text\nReading field: Ljava/util/List; - children\n                  OpCode: 0x70 -- TC_NULL (at offset 0x8EB)\n                * L children: None\n```\n\nInside the binary it looks like: 0x70 (null) 0x78 (endblock)\nI don't know what object needs to read that endblock, but that one is skewing the further reading of the file.","author":{"url":"https://github.com/svaningelgem","@type":"Person","name":"svaningelgem"},"datePublished":"2025-06-09T06:23:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/60/python-javaobj/issues/60"}