Summary of several methods for Django to accept front-end data

Background

Halfway through writing the test toolbox, I encountered a problem with front-end and back-end data interaction today, so let’s sort it out together.

Environment

------------------------------------------------ -----------

Version related

Operating system: Mac OS -------------------------------------------------- --

Note: I tested the Get method, and the POST method is also applicable.

Character type

Character type data is relatively easy to obtain. The front-end transfer method is as follows:

sendData = {
  "exporttype": exporttype,

  "bugids": bugids,

  "test": JSON.stringify({"test": "test"})

};

Note: In Python2.7, the data is unicode encoded. If you want to use it, sometimes you need to convert str

Result example:

Excle

Array type

Get array type If you use the method of obtaining string data, the result will be None. We need to use this method:

bugids = request.GET.getlist("bugids[]")

The data obtained in this way is of array type.

Note: The elements in the obtained array are unicode encoded and need to be transcoded at some point. Result examples:

•The passed url

[14/Jul/2016 11:00:41]"GET /testtools/exportbug/?exporttype=Excle&bugids%5B%5D=102&bugids%

[u'102', u'101', u'100', u'99', u'98', u'97', u'96', u'95', u'94', u'93', u'92', u'91', u

character data can actually be processed as string data. After obtaining the corresponding string, just use the JSON module to format it.

For the front end, the typical data to pass is to pass JSON data, so the method used is:

"test": JSON.stringify({"test": "test"})

Example of results:

{"test":"test"}

Related source code

•Get method

The Get method is a method in wsgi.

def GET(self):
    # The WSGI spec says 'QUERY_STRING' may be absent.
    raw_query_string = get_bytes_from_wsgi(self.environ, 'QUERY_STRING', '')
    return http.QueryDict(raw_query_string, encoding=self._encoding)

The final return is a http.QueryDict(raw_query_string, encoding=self._encoding)http's original data, and QueryDict inherits from MultiValueDict , so we can just look at MultiValueDict directly.

•MultiValueDict

In fact, the source code does not look difficult.

def get(self, key, default=None):
    """
    Returns the last data value for the passed key. If key doesn't exist
    or value is an empty list, then default is returned.
    """
    try:
      val = self[key]
    except KeyError:
      return default
    if val == []:
      return default
    return val
  
  def getlist(self, key, default=None):
    """
    Returns the list of values for the passed key. If key doesn't exist,
    then a default value is returned.
    """
    try:
      return super(MultiValueDict, self).__getitem__(key)
    except KeyError:
      if default is None:
        return []
      return default
  
  def __getitem__(self, key):
    """
    Returns the last data value for this key, or [] if it's an empty list;
    raises KeyError if not found.
    """
    try:
      list_ = super(MultiValueDict, self).__getitem__(key)
    except KeyError:
      raise MultiValueDictKeyError(repr(key))
    try:
      return list_[-1]
    except IndexError:
      return []

The getlist method is to integrate all the data and return it.

The above summary of several methods for Django to accept front-end data is all the content shared by the editor. I hope it can give you a reference. For more related articles, please pay attention to the PHP Chinese website (m.sbmmt.com)!

.