SelfHost 1.3 vs SelfHost 1.2

[SPiercer]

i noticed that the newer version of the selfhost (1.3) doesn't redirect the host to /index.html by default you have to type the url localhost/index.html and sometimes causes caching errors while the older version (1.2) works perfectly fine i don't see what's the problem here maybe you could check this kind of issue for us

[Leeful]

Thanks for the question. The reason v1.3 works like that is completely intentional.

My Exploit Host server was originally made for my original exploit menu then X-Project then PS-Phwaor!. The problem was that X-Project is very fussy and it will not work from offline cache if /index.html is not used.

Myself and KiiWii were over run by people saying that X-Project did not work from cache and this was all because they did not include the /index.html in the URL even though they were clearly advised to.

The solution was to make v1.3 not work if index.html was not included in the URL. This solved the problem and stopped the bombardment of questions asking why X-Project would not cache properly. :)

[SPiercer]

i see... seems interesting

and by the way i made some modifications to your host and added some interesting things most of them are under testing right now but what seemed to work fine is the auto load function, in general i added a button underneath all buttons that when pressed it automatically auto load the selected function each time you open up the page ... if you like to see the code i'd be glad to send it to you mate <3 :)

On Thu, 13 Aug 2020 at 00:52, Leeful notifications@github.com wrote:

Thanks for the question. The reason v1.3 works like that is completely intentional.

My Exploit Host server was originally made for my original exploit menu then X-Project then PS-Phwaor!. The problem was that X-Project is very fussy and it will not work from offline cache if /index.html is not used.

Myself and KiiWii were over run by people saying that X-Project did not work from cache and this was all because they did not include the /index.html in the URL even though they were clearly advised to.

The solution was to make v1.3 not work if index.html was not included in the URL. This solved the problem and stopped the bombardment of questions asking why X-Project would not cache properly. :)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Leeful/leeful.github.io/issues/3#issuecomment-673148512, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ625GQJQA2QNVH5Y32DQT3SAMML3ANCNFSM4P3LLUNA .

[Leeful]

Thanks, yeah I'd love to have a look. I've no intention in doing anything like that to these menu though. They are just there to test the exploit an payloads. Thats why I've kept them as basic as possible. I'll leave things like that for when I update PS-Phwoar.

Are you using cookies to autoload?

[SPiercer]

well not exactly, i don't use cookies but instead i used LocalStorage its much much better and more stable than cookies cuz i work in a that kind of ps4 service store and sometimes some PS4s doesn't save cookies well and doesn't work all the time so i use LocalStorage and jQuery since it's inside the HTML5 so it's more stable

and i'll be doing some final modifications now to the autoload functions and i'll be sending them to you

and if you like any help with the PS-Phwoar i'd be glad to help cuz i got lots of freetime early in the morning shift

Finally, I'm a senior flutter developer so if you need any cross-platform application (Android,iOS,Desktop,Web and embedded systems) i can do it for you with great ease.

and if you got a different method for contact that would be much better if we're going to work together later on

much love. N.