Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Django users
Home
+ new post
About this group
Join this group
Message from discussion Javascript encoding and python decoding and vice versa
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Kurtis Mullins  
View profile  
 More options Oct 11 2012, 12:10 pm
From: Kurtis Mullins <kurtis.mull...@gmail.com>
Date: Thu, 11 Oct 2012 12:09:08 -0400
Local: Thurs, Oct 11 2012 12:09 pm
Subject: Re: Javascript encoding and python decoding and vice versa
Print | View thread | Show original | Report this message | Find messages by this author

Thanks, Javier. I actually did not realize that the connection was
encrypted prior to sending the entire stream. I (mistakenly) assumed it
simply secured the body but that doesn't even sound remotely right now that
I put more thought into it. That makes a whole lot more sense!

On the other hand, some valid points raised against storing sensitive data
in a Query String:
http://stackoverflow.com/questions/323200/is-a-https-query-string-secure

On Thu, Oct 11, 2012 at 11:59 AM, Javier Guerra Giraldez <jav...@guerrag.com

> wrote:
> On Thu, Oct 11, 2012 at 10:25 AM, Kurtis Mullins
> <kurtis.mull...@gmail.com> wrote:
> > Sorry, you're probably right. I imagine there are no security risks
> related
> > to pulling a host-name from a DNS server. However, I do not know if the
> case
> > is the same for an HTTP Proxy when the query is included in the URL.

> a malicious DNS would lead the client to a rogue server, but if the
> client checks the server certificate, it wouldn't fly (that's what i
> meant by "sever identity verification")

> a malicious HTTP proxy rarely would be transparent.  Even in that
> case, it would only see who is communicating with who.  The whole
> stream (including the HTTP verbs, URL, parameters, bodies, etc) is
> opaque if encrypted with SSL.  That's why you should always use https.

> --
> Javier

> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google