Javascript 7
ViCQ wrote: I think I know why this works for some people but not others. I just tried this again myself, using chrome, and it didn't work.
So then I did it again using Firefox and it worked!
Hope this helped.
Yup !! you're right !! just tried on chrome and IE ….. it didn't work !!! it worked fine for me on firefox !!
I had the same issue, and i got around it without giving that 5th variable a value. I'm not quite sure what Kyk and Phohtoo are going on about… Maybe I just overlooked something or didn't notice when i did it. Before assigning values to anything though, try doing it in FF, it worked right away for me too.
Good luck!
Well all I can say is that you get:
http://i68.photobucket.com/albums/i19/crazy_sniper/NotFound.jpg
when using Chrome; I just redid the challenge. Firefox works.
Considering I havn't even done this challenge, I'm not saying Moshbat is wrong, however chrome does seem to do a lot of very weird things. One really annoying example is how the text that should by displayed, as I can see from the source when I press ctrl+U, will be different than the actual text displayed on the page when on some PHP pages.
I think the mission's broken or something. I manipulated the JavaScript code(after correcting the format) into printing the password . I returns "*F__"(obviously without the quotes, the asterixes represent a number. The same goes for the underscores). I tried to input it into the password box. It does nnot return the "wrong!" message it does when the password is wrong. It redirects me to the *F__.php page. This returns a 404. And this is happening in IE, Chrome and Firefox, all of them(although it really doesn't matter what the browser is sincce it returns a 404)
goluhaque wrote: I think the mission's broken or something. I manipulated the JavaScript code(after correcting the format) into printing the password . I returns "*F__"(obviously without the quotes, the asterixes represent a number. The same goes for the underscores). I tried to input it into the password box. It does nnot return the "wrong!" message it does when the password is wrong. It redirects me to the *F__.php page. This returns a 404. And this is happening in IE, Chrome and Firefox, all of them(although it really doesn't matter what the browser is sincce it returns a 404)
Hmm … I wonder if 'f' and 'F' are the same thing …
MoshBat wrote: [quote]Twinkee wrote: [quote]goluhaque wrote: I think the mission's broken or something. I manipulated the JavaScript code(after correcting the format) into printing the password . I returns "*F__"(obviously without the quotes, the asterixes represent a number. The same goes for the underscores). I tried to input it into the password box. It does nnot return the "wrong!" message it does when the password is wrong. It redirects me to the *F__.php page. This returns a 404. And this is happening in IE, Chrome and Firefox, all of them(although it really doesn't matter what the browser is sincce it returns a 404)
Hmm … I wonder if 'f' and 'F' are the same thing … [/quote] Losing my patience. No, they are not the same. And did anyone notice a bit about the case of the string, huh?[/quote]
Wow dude really? It was a hint, I didn't want to outright say use 'f' instead of 'F'.
Sorry about necroing this thread, but I've tried this with IE, FF, and Chrome. Looking at the page source in each one, Chrome includes two lines that initialize two key variables, while neither of the others do. I also used a JS alert to show what the password is and it matched what I got when I worked through the source code in Chrome.
Now, in all the browsers, that password gets me past the dialogs (so it's definitely correct), but in all of them, it leads to a 404. Could it be that whoever codes that challenge accidentally removed parts of the source code and deleted the final page? But that doesn't explain why the source code is different in Chrome than in IE and FF.
YouGotHacked wrote: Sorry about necroing this thread, but I've tried this with IE, FF, and Chrome. Looking at the page source in each one, Chrome includes two lines that initialize two key variables, while neither of the others do. I also used a JS alert to show what the password is and it matched what I got when I worked through the source code in Chrome.
Now, in all the browsers, that password gets me past the dialogs (so it's definitely correct), but in all of them, it leads to a 404. Could it be that whoever codes that challenge accidentally removed parts of the source code and deleted the final page? But that doesn't explain why the source code is different in Chrome than in IE and FF.
You may PM me if you like.
I went over the source code again - it's the same for all browsers. In FF and IE, the two key lines are whitespaced really far to the right. Chrome cleaned up the whitespace automatically, which made me (and some other people, too, I think) believe the source code was different.
EDIT: Problem resolved. The case handling threw me off since I was working in uppercase anyway. Changed case and it worked.
The challenge works the issue is not based on the browser, it is based in the code when a correct password is given.
I got a 404 error myself but, if you look in the source code when you get a correct answer what it does you might get a clue on how to fix that 404 error.
here is the issue –> the password must be submitted in pce –> the credit file must be in wce in the URL
when the script takes the correct password and does the redirect to the file to get credit you'll get a 404 error because the c**e doesn't match the file on the server.
sorry if this was any kind of spoiler, that was not my intention, if you already have the correct answer this should help you get credit for the mission.