[Page shows insecure content warning, but not for all users]

Thanks for an insulting post.

[Page shows insecure content warning, but not for all users]

No, that doesn't explain why it's only for some users.

 

It's clearly an issue with the jQuery "backstretch" plugin. Has something to do with people and very large screens/resolutions. Still doesn't make sense.

[Can I add a tick box to a form output from MYSQL?]

What is wrong with what you have here? Does it work?

[Page shows insecure content warning, but not for all users]

A customer's web page of their store (where credit card numbers are entered) is HTTPS. On my machine, and for several others, there are no content warnings; everything is HTTPS. For some users, the page shows that some content is insecure. How is this possible?

 

I should note there is a backstretch jQuery script in use, but I've set the background to always be HTTPS, so it doesn't make too much sense that this is the culprit.

[Why is my HTTPS form posting to the HTTP page?]

The answer here was that there was a <base> element on the page that I forgot about. This <base> tag had the href in HTTP, not HTTPS. Eh voila.

[Why is my HTTPS form posting to the HTTP page?]

The only additional information I have is that based on browser settings, a user might get "although this page is encrypted the information you have entered is to be sent over an unencrypted network."

 

This still doesn't make sense. It is an HTTPS page with a relative URL. How can it be posting as HTTP? Ugh.

[Why is my HTTPS form posting to the HTTP page?]

(sent a private message with URL)

[Code works. .htaccess modifications work. They don't work together.]

Now that I'm closer to a solution, I'm finding exactly what's going on. Closing this topic and opened a new one:

http://www.phpfreaks.com/forums/index.php?topic=359062.0

[Why is my HTTPS form posting to the HTTP page?]

If I'm on https://myserver.com/test.php, why is this form posting to the HTTP version of the page?

 

<form method="post" action="test.php?step=1">
<input type="text" name="email">
<input type="submit" name="submit">
</form>

 

I can hard-code the full path in the action, but that seems unnecessary.

 

Further, I have some pages where it posts to HTTPS first (as I expect). Why would it go to one versus another?

[Code works. .htaccess modifications work. They don't work together.]

Actually I see now that the $_POST has nothing in it. Is the mod_rewrite eliminating the post on redirect?

[Move topic to the correct forum]

Appreciate it.

[Move topic to the correct forum]

Can someone move this to the right place?

http://www.phpfreaks.com/forums/index.php?topic=347820.msg1641283#msg1641283

 

It was put in mod_rewrite, but that was not the issue. The question was how to modify the client because mod_rewrite was using virtual paths. The answer was to use the "base" tag. This is not a mod_rewrite problem.

[Code works. .htaccess modifications work. They don't work together.]

I don't understand why I'm breaking spec by using header( "location:abcd" ). Can you explain?

 

Which redirect do you think I should comment out? As explained before, the code works just fine. The only error is when .htaccess is then configured to ensure pages are HTTPS.

 

What do you mean "dump the data instead"?

[Code works. .htaccess modifications work. They don't work together.]

This one requires lots of up front information:

 

[*]I have a page, for this example that I will call page.php. It takes get parameters, and for this example I'll call the parameter "step". So I have a URL like this: page.php?step=1

[*]This page has a form with an action of page.php?step=1.

[*]The code on the page validates the posting information. If the information is bad, it returns the user to page.php?step=1; if it is good, it takes the user to page.php?step=2 via header( "location:page.php?step=2" ). So redirection is done by relative path, not full URLs.

 

This all works as expected.

 

Now what I've done is set .htaccess to be HTTPS for this page, via this code:

 

# Turn SSL on for payments

RewriteCond %{HTTPS} off

RewriteCond %{SCRIPT_FILENAME} \/page\.php [NC]

RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]

 

This works (initially). However, once you try to post the form, it just redirects back to the step=1 version of the page. I really don't know how or why that would be.

 

I'm not sure how else I can explain this or what other information you may have. But it's frustrating to not get a page working in HTTPS that works in HTTP. Very odd. Any suggestions? (I don't even really know the best location to figure out when/why it's redirecting back to the original page.)

 

 

[Variables from first function affected by same name in second function]

http://stackoverflow.com/questions/6038958/javascript-for-loop-index-variables-become-part-of-global-scope I guess that is the answer. Sigh.

[Variables from first function affected by same name in second function]

If something calls function f1 below, what do you expect to see in the alert?

 

	function f1()
	{
	  for ( i = 0; i < 8; i++ )
	  {
	     other_func();
	     alert( i );
	  }
	}

	function other_func()
	{
	  for ( i = 0; i < 100; i++ )
	  {
	  }
	}

 

The answer is 100, and we've found this to be quite odd. If either of the functions used "var i" instead of just "i" in the loop, you'd get 0, 1, 2,...

 

Why is this, exactly?

[onsubmit synchronous ajax validation]

Update: I changed the code to this, and it works. I guess I need to return the variable outside the success handler, according to some google results I found.

 

function are_quantities_valid() {	
toReturn = false;

$.ajax( "server_file.php", {
	async: false,
	data: {
		sid: the_session_id
	}, 
	success: function ( data ) { 			
		if ( data == "true" )
			toReturn = true;
		else
			alert( data );
	}
});

return toReturn;
}

[onsubmit synchronous ajax validation]

I'm trying to do a synchronous call for a form's onsubmit function. The server-side code returns "true" or an error message. The problem is that the code that should not be reached (see example below) is actually reached.

 

The "should not be reached" code is only there for this example; without it, the function returns true even though an error message was displayed to the user.

 

So I guess I'm just asking for some help on synchronous ajax form validations. Am I not doing it right?

 

function are_quantities_valid() {	
$.ajax( "server_file.php", {
	async: false,
	data: {
		sid: i_pass_the_session_id_to_the_server
	}, 
	success: function ( data ) { 			
		if ( data == "true" )
			return true;

		alert( data );
		return false;
	}
});

alert( 'this should not be reached.' );
return false;
}

[Sortable table]

Um, yes, but I came here to see what other people have used and recommend.

[Sortable table]

I guess this looks promising: http://tablesorter.com/docs/

[Sortable table]

Oh, not that type of sort. this type of sort: http://briancrain.com/sheet-music/

[Sortable table]

Anyone used a good sortable table script? (JavaScript or Ajax)

 

I don't want to write my own, and I'm sure there are good ones out there. I just want to know what others have used. Only requirements are to sort all the visible rows, while keeping the header row.

[Loop not functioning as I expect]

Very good... thanks!

[Loop not functioning as I expect]

Right, but I thought it would be synchronous with the function returning data. Is there a way to make it synchronous?

[Loop not functioning as I expect]

As for the function(i), it is interesting that what you said works, but the results don't necessarily display in the grid in rows 1, 2, 3, etc. Any reason why they would be displayed in random order?

 

As for the other thing, it's a pretty complex form. A select box changes something, and based on that "something" we get a different list of rows in the table, and from there the user executes a function that calls this ajax.

 

Thank you in advance; you have been most helpful.